From: Bjorn Helgaas <helgaas@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Jim Quinlan <jim2101024@gmail.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Cyril Brulebois <kibi@debian.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
regressions@lists.linux.dev, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 1/4] Revert "PCI: brcmstb: Do not turn off WOL regulators on suspend"
Date: Thu, 12 May 2022 07:45:06 -0500 [thread overview]
Message-ID: <20220512124506.GA842977@bhelgaas> (raw)
In-Reply-To: <d66ec3a0-10b4-fd60-0b03-e9a3f3571645@leemhuis.info>
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@google.com>
> >
> > 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@debian.org>
> > 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:".
next prev parent reply other threads:[~2022-05-12 12:45 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 [this message]
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
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=20220512124506.GA842977@bhelgaas \
--to=helgaas@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=f.fainelli@gmail.com \
--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@leemhuis.info \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).