From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bart Van Assche <bvanassche@acm.org>,
scsi <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: Consider picking up "scsi: core: Fix a procfs host directory removal regression" for stable
Date: Mon, 20 Mar 2023 07:45:04 +0100 [thread overview]
Message-ID: <e6314dd6-df75-fff8-1e3c-546b2b44be5b@leemhuis.info> (raw)
In-Reply-To: <472c53aa-4803-cde9-8f80-cbd7d33dc9c5@leemhuis.info>
On 20.03.23 07:19, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi Greg. From https://bugzilla.kernel.org/show_bug.cgi?id=217215 it
> looks like you want to add be03df3d4bfe ("scsi: core: Fix a procfs host
> directory removal regression") to your stable queue. It lacks a stable
> tag, but fixes a bug in a commit that afaics was backported to all
> stable series last week.
>
> Side note: would you scripts have noticed this automatically and added
> it to the queue today? (Just wondering if this mail actually makes any
> difference.)
Sorry, ignore that, I noticed that fix is already in your queue (I
looked at it before writing that mail, but it seems I somehow missed it
and only noticed now; sorry for the noise).
Ciao, Thorsten
next prev parent reply other threads:[~2023-03-20 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 6:19 Consider picking up "scsi: core: Fix a procfs host directory removal regression" for stable Linux regression tracking (Thorsten Leemhuis)
2023-03-20 6:45 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-03-20 8:47 ` Greg KH
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=e6314dd6-df75-fff8-1e3c-546b2b44be5b@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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).