Linux-NVME Archive on lore.kernel.org
 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>
Subject: Re: [PATCH 1/1] Revert "nvme: don't bother to look up a namespace for controller ioctls"
Date: Thu, 22 Apr 2021 16:10:23 +0900	[thread overview]
Message-ID: <20210422071023.GA26038@localhost> (raw)
In-Reply-To: <20210422070735.25855-2-minwoo.im.dev@gmail.com>

On 21-04-22 16:07:35, Minwoo Im wrote:
> This reverts commit 3557a4409701a132e8f86ad234ac8cf6e97b052e.
> 
> If we simply retrieve namespace from the given subsystem, controller to
> be retrieved might not be the one which is really attached to the given
> namespace.  We should consider the namespace attachment with controllers
> in the subsystem, so this patch simply reverts the previous commit.
> 
> Signed-off-by: Minwoo Im <minwoo.im.dev@gmail.com>

Sorry, I missed the latest nvme-5.13 tree.  This will have conflicts
with the commit 2637baed7801 ("nvme: introduce generic per-namespace
chardev").

Please let me resend it.

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

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  7:07 [PATCH 0/1] nvme: fix controller ioctl through ns_head Minwoo Im
2021-04-22  7:07 ` [PATCH 1/1] Revert "nvme: don't bother to look up a namespace for controller ioctls" Minwoo Im
2021-04-22  7:10   ` Minwoo Im [this message]

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=20210422071023.GA26038@localhost \
    --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