From: Florian Fainelli <f.fainelli@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Jim Quinlan <jim2101024@gmail.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Cyril Brulebois <kibi@debian.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
regressions@lists.linux.dev, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 0/4] PCI: brcmstb: Revert subdevice regulator stuff
Date: Mon, 13 Jun 2022 10:06:12 -0700 [thread overview]
Message-ID: <e58125a4-f885-ae55-0441-d52ecab9a1e8@gmail.com> (raw)
In-Reply-To: <20220511203948.GA811126@bhelgaas>
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@google.com>
>>>
>>> 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@mail.gmail.com
>
> 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
next prev parent reply other threads:[~2022-06-13 17:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 20:18 [PATCH 0/4] PCI: brcmstb: Revert subdevice regulator stuff Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 1/4] Revert "PCI: brcmstb: Do not turn off WOL regulators on suspend" Bjorn Helgaas
2022-05-12 6:24 ` Thorsten Leemhuis
2022-05-12 12:45 ` Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 2/4] Revert "PCI: brcmstb: Add control of subdevice voltage regulators" Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 3/4] Revert "PCI: brcmstb: Add mechanism to turn on subdev regulators" Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 4/4] Revert "PCI: brcmstb: Split brcm_pcie_setup() into two funcs" Bjorn Helgaas
2022-05-11 20:24 ` [PATCH 0/4] PCI: brcmstb: Revert subdevice regulator stuff Florian Fainelli
2022-05-11 20:39 ` Cyril Brulebois
2022-05-11 20:54 ` Florian Fainelli
2022-05-11 20:39 ` Bjorn Helgaas
2022-06-13 17:06 ` Florian Fainelli [this message]
2022-06-14 0:00 ` Bjorn Helgaas
2022-06-14 16:16 ` Florian Fainelli
2022-06-14 18:59 ` Jim Quinlan
2022-06-21 23:32 ` Bjorn Helgaas
2022-06-27 23:18 ` Bjorn Helgaas
2022-07-01 11:25 ` Jim Quinlan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e58125a4-f885-ae55-0441-d52ecab9a1e8@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jim2101024@gmail.com \
--cc=kibi@debian.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nsaenz@kernel.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.