From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [bugzilla-daemon@kernel.org: [Bug 216109] New: Steam Deck fails to boot when E820 entries clipped out of _CRS] #forregzbot
Date: Sun, 19 Jun 2022 14:37:40 +0200 [thread overview]
Message-ID: <2c6bd8f9-e466-50d0-0d24-0ec334db37cb@leemhuis.info> (raw)
In-Reply-To: <d4ea2dd2-2e89-d3a2-ee5c-f64bb1b8f576@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 12.06.22 13:11, Thorsten Leemhuis wrote:
>> Subject: [Bug 216109] New: Steam Deck fails to boot when E820 entries clipped
>> out of _CRS
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=216109
#regzbot fixed-by: a2b36ffbf5b6
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
prev parent reply other threads:[~2022-06-19 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 22:43 [bugzilla-daemon@kernel.org: [Bug 216109] New: Steam Deck fails to boot when E820 entries clipped out of _CRS] Bjorn Helgaas
2022-06-10 11:14 ` Hans de Goede
2022-06-12 11:11 ` Thorsten Leemhuis
2022-06-19 12:37 ` 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=2c6bd8f9-e466-50d0-0d24-0ec334db37cb@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--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).