From: Greg KH <greg@kroah.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Sasha Levin <sashal@kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] scsi: Fix handling of host-aware ZBC disks
Date: Fri, 18 Sep 2020 08:04:00 +0200 [thread overview]
Message-ID: <20200918060400.GA58093@kroah.com> (raw)
In-Reply-To: <CY4PR04MB3751FEC907B8C0FD50B53624E73E0@CY4PR04MB3751.namprd04.prod.outlook.com>
On Thu, Sep 17, 2020 at 11:50:44PM +0000, Damien Le Moal wrote:
> On 2020/09/18 0:53, Sasha Levin wrote:
> > Hi
> >
> > [This is an automated email]
> >
> > This commit has been processed because it contains a "Fixes:" tag
> > fixing commit: b72053072c0b ("block: allow partitions on host aware zone devices").
> >
> > The bot has tested the following trees: v5.8.9.
> >
> > v5.8.9: Failed to apply! Possible dependencies:
> > a3d8a2573687 ("scsi: sd_zbc: Improve zone revalidation")
> >
> >
> > NOTE: The patch will not be queued to stable trees until it is upstream.
> >
> > How should we proceed with this patch?
> >
>
> Usually, I wait for Greg's bots to ping me and then I send a fixed up backported
> patch for stable. Would that work ? I can backport now if needed.
That works, no worries, thanks.
greg k-h
prev parent reply other threads:[~2020-09-18 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200915073347.832424-2-damien.lemoal@wdc.com>
2020-09-17 15:53 ` [PATCH v3 1/2] scsi: Fix handling of host-aware ZBC disks Sasha Levin
2020-09-17 23:50 ` Damien Le Moal
2020-09-18 6:04 ` Greg KH [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=20200918060400.GA58093@kroah.com \
--to=greg@kroah.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sashal@kernel.org \
--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).