From: willy@linux.intel.com (Matthew Wilcox)
Subject: [PATCH] NVMe: replace nvme_ns with nvme_dev for user admin
Date: Thu, 26 Jul 2012 12:24:55 -0400 [thread overview]
Message-ID: <20120726162455.GF22985@linux.intel.com> (raw)
In-Reply-To: <1343254075-439-1-git-send-email-keith.busch@intel.com>
On Wed, Jul 25, 2012@04:07:55PM -0600, Keith Busch wrote:
> The function nvme_user_admin_command does not require a namespace to proceed.
> Replace with the nvme_dev structure so that it can be called from contexts that
> do not have a namespace.
Thanks, applied.
prev parent reply other threads:[~2012-07-26 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 22:07 [PATCH] NVMe: replace nvme_ns with nvme_dev for user admin Keith Busch
2012-07-26 16:24 ` Matthew Wilcox [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=20120726162455.GF22985@linux.intel.com \
--to=willy@linux.intel.com \
/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).