Bjorn,
On 5/11/22 13:39, Bjorn Helgaas wrote:
On Wed, May 11, 2022 at 01:24:55PM -0700, Florian Fainelli wrote:
On 5/11/22 13:18, Bjorn Helgaas wrote:
From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
Cyril reported that 830aa6f29f07 ("PCI: brcmstb: Split brcm_pcie_setup()
into two funcs"), which appeared in v5.17-rc1, broke booting on the
Raspberry Pi Compute Module 4. Revert 830aa6f29f07 and subsequent patches
for now.
How about we get a chance to fix this? Where, when and how was this even
reported?
Sorry, I forgot to cc you, that's my fault:
https://lore.kernel.org/r/CABhMZUWjZCwK1_qT2ghTSu2dguJBzBTpiTqKohyA72OSGMsaeg@xxxxxxxxxxxxxx
If you come up with a fix, I'll drop the reverts, of course.
OK, so now this patch series has landed in Linus' tree and was committed
on May 31st and we got no notification that this patch series was applied :/
How did I notice? Because suddenly the stable auto selection started to
email me about the 4 reverts being included which is kind of the worse
way to know about a patch having been applied.
What is even better is that meanwhile there was already a candidate fix
proposed on May 18th, and a v2 on May 28th, so still an alternative to
the reverts making it to Linus' tree, or so I thought.
This utterly annoys me because:
- the history for pcie-brcmstb.c is now looking super ugly because we
have 4 commits getting reverted and if we were to add back the original
feature being added now what? Do we come up with reverts of reverts, or
the modified (with the fix) original commits applied on top, are not we
going to sign ourselves for another 13 or so round of patches before we
all agree on the solution?
- we could have just fixed this with proper communication from the get
go about the regression in the first place, which remains the failure in
communicating appropriately with driver authors/maintainers
- v5.17 and v5.18 final were already broken, but who on earth uses v5.17
or v5.18 and not their stable counter parts, so we had a chance of
slipping in a fix in a subsequent stable, I mean, it's been broken for 2
releases on the CM4 and it was not noticed, so what was the urgency?
- the reverts will make it to -stable being bug fixes for regressions,
however for users like Jim and I, now we will lose a feature that we
were relying on, thus causing a regression for *many other* platforms
than just the CM4
I appreciate that as a maintainer you are very sensitive to regressions
and want to be responsive and responsible but this is not leaving just a
slightest chance to right a wrong. Can we not do that again please?
Maybe I am being overly sensitive and disgruntled today, but really this
is the type of thing that makes me want to quit working on the Linux kernel.
--
Florian
