Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	kch@nvidia.com
Cc: linux-nvme@lists.infradead.org
Subject: [PATCH RFC 0/3] set nvme ns's vwc respectively
Date: Mon,  4 Nov 2024 16:54:59 +0800	[thread overview]
Message-ID: <20241104085524.118221-1-kanie@linux.alibaba.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 724 bytes --]

Hi,
  These patches are supporting separate vwc attr for each namespace.

  I found that the number 2 and 3 patch are conflict with Matias Bjørling's
patch which implement to supporting rotational device, this is the first
time this happend to me, I dont know how to handle this, so there is a "RFC"
tag in tittle, waiting for the solution.

Guixin Liu (3):
  nvme: check ns's volatile write cache not present
  nvme: query independent identify ns by default
  nvmet: report ns's vwc not present

 drivers/nvme/host/core.c        | 11 +++++-----
 drivers/nvme/target/admin-cmd.c | 36 +++++++++++++++++++++++++++++++++
 include/linux/nvme.h            |  1 +
 3 files changed, 43 insertions(+), 5 deletions(-)

-- 
2.43.0



             reply	other threads:[~2024-11-04  8:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  8:54 Guixin Liu [this message]
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
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=20241104085524.118221-1-kanie@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --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