From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [Bug 215925] New: PCIe regression on Raspberry Pi Compute Module 4 (CM4) breaks booting #forregzbot
Date: Mon, 20 Jun 2022 09:00:00 +0200 [thread overview]
Message-ID: <2bf69b55-a8fa-38cb-68f4-fd762877ac32@leemhuis.info> (raw)
In-Reply-To: <3aa008b9-e477-3e6d-becb-13e28ea91f10@leemhuis.info>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 09.05.22 09:44, Thorsten Leemhuis wrote:
> [TLDR: I'm adding this regression report to the list of tracked
> regressions; all text from me you find below is based on a few templates
> paragraphs you might have encountered already already in similar form.]
>
> On 02.05.22 20:38, Bjorn Helgaas wrote:
>> On Sat, Apr 30, 2022 at 2:53 PM <bugzilla-daemon@kernel.org> wrote:
>>>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=215925
#regzbot fixed-by: f4fd559de3434c44
prev parent reply other threads:[~2022-06-20 7:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215925-41252@https.bugzilla.kernel.org/>
2022-05-02 18:38 ` [Bug 215925] New: PCIe regression on Raspberry Pi Compute Module 4 (CM4) breaks booting Bjorn Helgaas
2022-05-09 7:44 ` Thorsten Leemhuis
2022-05-09 17:07 ` Bjorn Helgaas
2022-05-09 17:45 ` Cyril Brulebois
2022-05-10 17:22 ` Bjorn Helgaas
2022-05-10 20:07 ` Cyril Brulebois
2022-05-10 20:55 ` Bjorn Helgaas
2022-05-16 21:05 ` Jim Quinlan
2022-05-18 19:47 ` Jim Quinlan
2022-05-20 5:48 ` Thorsten Leemhuis
2022-06-20 7:00 ` Thorsten Leemhuis [this message]
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=2bf69b55-a8fa-38cb-68f4-fd762877ac32@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-pci@vger.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 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).