On Thu, May 12, 2022 at 08:24:00AM +0200, Thorsten Leemhuis wrote:
> On 11.05.22 22:18, Bjorn Helgaas wrote:
> > From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
> >
> > This reverts commit 11ed8b8624b8085f706864b4addcd304b1e4fc38.
> >
> > This is part of a revert of the following commits:
> >
> > 11ed8b8624b8 ("PCI: brcmstb: Do not turn off WOL regulators on suspend")
> > 93e41f3fca3d ("PCI: brcmstb: Add control of subdevice voltage regulators")
> > 67211aadcb4b ("PCI: brcmstb: Add mechanism to turn on subdev regulators")
> > 830aa6f29f07 ("PCI: brcmstb: Split brcm_pcie_setup() into two funcs")
> >
> > 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. Apparently 830aa6f29f07 panics with an
> > Asynchronous SError Interrupt, and after further commits here is a black
> > screen on HDMI and no output on the serial console.
> >
> > This does not seem to affect the Raspberry Pi 4 B.
> >
> > Reported-by: Cyril Brulebois <kibi@xxxxxxxxxx>
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215925
>
> A "Bugzilla" tag? Why don't you just use a proper "Link:" tag, as
> explained by the documentation to use in this case (I clarified the docs
> recently with regards to this). Such inventions (some people use
> "References:", others "BugLink:" and there were a few others I already
> forget about) make my regression tracking efforts hard. :-/
In this case, I actually looked through the history to try to figure
out the most common way to cite bugzilla but didn't see much
uniformity.
Anyway, I updated these to "Link:".
