linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Minwoo Im <minwoo.im.dev@gmail.com>
Subject: [PATCH V2 0/1] nvme: fix controller ioctl through ns_head
Date: Thu, 22 Apr 2021 17:04:06 +0900	[thread overview]
Message-ID: <20210422080407.62999-1-minwoo.im.dev@gmail.com> (raw)

Hello,

This series is to fix controller ioctl through the ns_head block device
and the per-namespace generic device.  This patch is mostly manual
revert for the commit 3557a4409701 ("nvme: don't bother to look up a
namespace for controller ioctls") with few more updates to the generic
device.

Please review.

Thanks,

Since V1:
  - Manually revert 3557a4409701 ("nvme: don't bother to look up a
    namespace for controller ioctls").  (Christoph)
  - Updates nvme_ns_head_chr_ioctl() which has been newly added for
    generic per-namespace chardev.

Minwoo Im (1):
  nvme: fix controller ioctl through ns_head

 drivers/nvme/host/core.c  | 22 -------------
 drivers/nvme/host/ioctl.c | 65 ++++++++++++++++++++++++---------------
 drivers/nvme/host/nvme.h  |  1 -
 3 files changed, 41 insertions(+), 47 deletions(-)

-- 
2.27.0


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

             reply	other threads:[~2021-04-22  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  8:04 Minwoo Im [this message]
2021-04-22  8:04 ` [PATCH V2 1/1] nvme: fix controller ioctl through ns_head Minwoo Im
2021-04-28  6:44 ` [PATCH V2 0/1] " Christoph Hellwig

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=20210422080407.62999-1-minwoo.im.dev@gmail.com \
    --to=minwoo.im.dev@gmail.com \
    --cc=axboe@fb.com \
    --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;
as well as URLs for NNTP newsgroup(s).