linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: "hch@infradead.org" <hch@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Sagi Grimberg <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [GIT PULL] nvme updates for 5.10
Date: Mon, 28 Sep 2020 09:13:07 +0000	[thread overview]
Message-ID: <CY4PR04MB375113383F128C96A4CC8F01E7350@CY4PR04MB3751.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200928060333.GA7431@infradead.org

On 2020/09/28 15:03, hch@infradead.org wrote:
> On Mon, Sep 28, 2020 at 01:53:46AM +0000, Damien Le Moal wrote:
>>>  - support ZNS in nvmet passthrough mode (Chaitanya Kulkarni)
>>>  - fix nvme_ns_report_zones (me)
>>
>> Shouldn't this one go into 5.9-rc7 as a fix ?
> 
> It is a fix, but not a critical one given that ZNS has just shown up
> and does not have any real products yet.  I'd still go for 5.9 if we
> didn't have dependencies on it that are going to shop up for 5.10.
> 
> So 5.10 for now. 5.9-stable pretty soon.

OK. Thanks !


-- 
Damien Le Moal
Western Digital Research

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-09-28  9:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27  7:23 [GIT PULL] nvme updates for 5.10 Christoph Hellwig
2020-09-28  1:53 ` Damien Le Moal
2020-09-28  6:03   ` hch
2020-09-28  9:13     ` Damien Le Moal [this message]
2020-09-28 15:03 ` Jens Axboe
2020-10-08 14:10 Christoph Hellwig
2020-10-08 14:52 ` Jens Axboe
2020-10-08 14:56   ` Christoph Hellwig
2020-10-08 14:57     ` Jens Axboe
2020-10-08 15:01 Christoph Hellwig
2020-10-08 15:48 ` Jens Axboe

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=CY4PR04MB375113383F128C96A4CC8F01E7350@CY4PR04MB3751.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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).