> makes breaking, unreviewed changes in kernel,

And reverted them as soon as the issue became apparent.

> then flames the maintainer who was working on cleanly updating the kernel for the not-yet-released compiler?

Talking aboutchanges that he had not pushed by the time Linus published the release candidate.

Also the "not yet released" seems to be a red herring, as the article notes having beta versions of compilers in new releases is a tradition for some distros, so that should not be unexpected. It makes some sense since distros tend to stick to a compiler for each elease, so shipping a soon to be out of maintenance compiler from day one will only cause other issues down the road.