From: Christoph Hellwig <hch@lst.de>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH RFC 2/3] nvme: query independent identify ns by default
Date: Tue, 5 Nov 2024 12:11:06 +0100 [thread overview]
Message-ID: <20241105111106.GA1993@lst.de> (raw)
In-Reply-To: <20241104085524.118221-3-kanie@linux.alibaba.com>
On Mon, Nov 04, 2024 at 04:55:01PM +0800, Guixin Liu wrote:
> Query independent identify ns by default, if returning fail,
> go back to sending the "identify namespace data structure for the
> specified NSID or the namespace capabilities for the NVM Command
> Set(cns = 0)".
How is this related to the rest of the series?
next prev parent reply other threads:[~2024-11-05 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 8:54 [PATCH RFC 0/3] set nvme ns's vwc respectively Guixin Liu
2024-11-04 8:55 ` [PATCH RFC 1/3] nvme: check ns's volatile write cache not present Guixin Liu
2024-11-05 11:12 ` Christoph Hellwig
2024-11-04 8:55 ` [PATCH RFC 2/3] nvme: query independent identify ns by default Guixin Liu
2024-11-05 11:11 ` Christoph Hellwig [this message]
2024-11-05 20:03 ` Keith Busch
2024-11-06 1:52 ` Guixin Liu
2024-11-04 8:55 ` [PATCH RFC 3/3] nvmet: report ns's vwc not present Guixin Liu
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=20241105111106.GA1993@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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