Hacker News Reader

We can't really know as we can't see the author's patch, but given that (i) the guy answering is responsible for the whole CPU architecture in Linux and (ii) the author mourns his putative contributor badge but does not criticize the other patch, that's a bet I'm ready to take.

FYI

https://lists.ozlabs.org/pipermail/linuxppc-dev/2022-June/24...

https://lore.kernel.org/all/20220609133245.573565-1-mpe@elle...

It was stated by the maintainer as the reason for discarding the author's contribution.

What the maintainer actually said was [0]:

> Thanks for your patch, but I wanted to fix it differently. Can you try the patch below and make sure it fixes the bug for you?

Which to me, at least, reads very differently than claiming the author's patch is worse.

[0] https://lists.ozlabs.org/pipermail/linuxppc-dev/2022-June/24...

(Credit to nolist_policy for pointing this out upthread.)

Obviously the author is not going to say their fix was worse, but commenters on here have described why: https://news.ycombinator.com/item?id=37675544

see https://news.ycombinator.com/item?id=37692883