From: Irvin Cote <irvincoteg@gmail.com>
To: hch@lst.de
Cc: kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me,
linux-nvme@lists.infradead.org, Irvin Cote <irvincoteg@gmail.com>
Subject: [PATCH 0/3] Start to disable shared ns without multipating
Date: Tue, 30 May 2023 19:27:06 -0300 [thread overview]
Message-ID: <20230530222709.28682-1-irvincoteg@gmail.com> (raw)
Staring to disable support for shared namespaces without multipathing
enabled. This is not meant to be an exhaustive list but rather a start.
Irvin Cote (3):
nvme-Kconfig: updating MULTIPATH option's description
nvme-core: exit scan if shared ns but no multipath
nvme-core: changing comment on disk names in nvme_alloc_ns
drivers/nvme/host/Kconfig | 2 ++
drivers/nvme/host/core.c | 12 ++++++------
2 files changed, 8 insertions(+), 6 deletions(-)
--
2.40.1
next reply other threads:[~2023-05-30 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 22:27 Irvin Cote [this message]
2023-05-30 22:27 ` [PATCH 1/3] nvme-Kconfig: updating MULTIPATH option's description Irvin Cote
2023-05-30 22:27 ` [PATCH 2/3] nvme-core: exit scan if shared ns but no multipath Irvin Cote
2023-05-30 22:27 ` [PATCH 3/3] nvme-core: changing comment on disk names in nvme_alloc_ns Irvin Cote
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=20230530222709.28682-1-irvincoteg@gmail.com \
--to=irvincoteg@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@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