From: james_p_freyensee@linux.intel.com (Jay Freyensee)
Subject: [PATCH] *** Discovery feature fix in nvme-cli ***
Date: Thu, 28 Jul 2016 13:03:19 -0700 [thread overview]
Message-ID: <1469736200-6618-1-git-send-email-james_p_freyensee@linux.intel.com> (raw)
Since the only way to do the discovery feature of NVMe-over-Fabrics
is through nvme-cli, I thought it will be appropriate to send
a patch to this email list (if nothing more than to inform and educate).
I'll push this to Keith Busch (the nvme-cli owner).
Jay Freyensee (1):
nvme-cli: user-defined hostnqn option for discover
fabrics.c | 11 +++++++++++
1 file changed, 11 insertions(+)
--
2.4.3
next reply other threads:[~2016-07-28 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 20:03 Jay Freyensee [this message]
2016-07-28 20:03 ` [PATCH] nvme-cli: user-defined hostnqn option for discover Jay Freyensee
2016-07-28 20:20 ` Roy Shterman
2016-07-28 20:35 ` Keith Busch
2016-07-28 21:21 ` J Freyensee
[not found] ` <45CF57A8-206F-4353-9386-A0BB8158AB5A@mellanox.com>
2016-07-28 21:36 ` [PATCH] [RESEND] " J Freyensee
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=1469736200-6618-1-git-send-email-james_p_freyensee@linux.intel.com \
--to=james_p_freyensee@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).