From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: linux-mmc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] Bug 216420 - Unable to handle kernel NULL pointer dereference at virtual address 00000008 #forregzbot
Date: Wed, 7 Sep 2022 17:54:24 +0200 [thread overview]
Message-ID: <b395b2aa-3aa8-8f12-8629-23266fa108d3@leemhuis.info> (raw)
In-Reply-To: <29a5c3e3-a590-01dd-1a2b-8415cae4a292@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 28.08.22 13:44, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
>
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developer don't keep an eye on it, I decided to forward it (I
> hope I picked the right recipients for this mail):
>
> [...]
>
> #regzbot introduced: v5.19..v6.0-rc2
> https://bugzilla.kernel.org/show_bug.cgi?id=216420
> #regzbot ignore-activity
#regzbot fixed-by: 25af7406df591
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-09-07 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 11:44 [Regression] Bug 216420 - Unable to handle kernel NULL pointer dereference at virtual address 00000008 Thorsten Leemhuis
2022-08-29 11:50 ` Yann Gautier
2022-08-29 13:54 ` Yann Gautier
2022-08-29 21:35 ` Saravana Kannan
2022-09-04 11:20 ` Gabriel Francisco
2022-09-07 15:54 ` 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=b395b2aa-3aa8-8f12-8629-23266fa108d3@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@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).