From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Sasha Levin <sashal@kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "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: Thu, 17 Sep 2020 23:50:44 +0000 [thread overview]
Message-ID: <CY4PR04MB3751FEC907B8C0FD50B53624E73E0@CY4PR04MB3751.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200917155335.19CBF21D24@mail.kernel.org
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.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-09-18 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 7:33 [PATCH v3 0/2] Fix handling of host-aware ZBC disks Damien Le Moal
2020-09-15 7:33 ` [PATCH v3 1/2] scsi: " Damien Le Moal
2020-09-15 15:13 ` Christoph Hellwig
2020-09-15 15:20 ` Johannes Thumshirn
2020-09-17 15:53 ` Sasha Levin
2020-09-17 23:50 ` Damien Le Moal [this message]
2020-09-18 6:04 ` Greg KH
2020-09-15 7:33 ` [PATCH v3 2/2] scsi: Fix ZBC disk initialization Damien Le Moal
2020-09-15 15:16 ` Christoph Hellwig
2020-09-16 0:09 ` [PATCH v3 0/2] Fix handling of host-aware ZBC disks Martin K. Petersen
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=CY4PR04MB3751FEC907B8C0FD50B53624E73E0@CY4PR04MB3751.namprd04.prod.outlook.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.