[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220225161727.GC13845@lst.de>
Date: Fri, 25 Feb 2022 17:17:27 +0100
From: Christoph Hellwig <hch@....de>
To: Keith Busch <kbusch@...nel.org>
Cc: linux-nvme@...ts.infradead.org, linux-block@...r.kernel.org,
linux-crypto@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org, axboe@...nel.dk, hch@....de,
martin.petersen@...cle.com, colyli@...e.de,
Hannes Reinecke <hare@...e.de>,
Klaus Jensen <its@...elevant.dk>
Subject: Re: [PATCHv3 09/10] nvme: add support for enhanced metadata
On Tue, Feb 22, 2022 at 08:31:43AM -0800, Keith Busch wrote:
> @@ -918,6 +918,30 @@ static blk_status_t nvme_setup_discard(struct nvme_ns *ns, struct request *req,
> return BLK_STS_OK;
> }
>
> +static inline void nvme_set_ref_tag(struct nvme_ns *ns, struct nvme_command *cmnd,
Overly long line. But I don't think this should be marked inline anyway.
Otherwise this looks good:
Reviewed-by: Christoph Hellwig <hch@....de>
I suspect eventually we'll need to lift the new Identify call into
the common revalidation once more fields get added there.
Powered by blists - more mailing lists