From: james_p_freyensee@linux.intel.com (Jay Freyensee)
Subject: [PATCH] nvme-cli: match treq value names to spec
Date: Wed, 7 Sep 2016 15:43:26 -0700 [thread overview]
Message-ID: <1473288206-16121-1-git-send-email-james_p_freyensee@linux.intel.com> (raw)
Fabrics spec uses "not specified" as one of the values for treq,
just like other discovery parameters (like rdma_prtype).
Signed-off-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
---
fabrics.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fabrics.c b/fabrics.c
index 18e961c..e7e3c56 100644
--- a/fabrics.c
+++ b/fabrics.c
@@ -116,7 +116,7 @@ static inline const char *nqntype_str(__u8 nqntype)
}
static const char * const treqs[] = {
- [NVMF_TREQ_NOT_SPECIFIED] = "unspecified transport requirements",
+ [NVMF_TREQ_NOT_SPECIFIED] = "not specified",
[NVMF_TREQ_REQUIRED] = "required",
[NVMF_TREQ_NOT_REQUIRED] = "not required",
};
--
2.7.4
next reply other threads:[~2016-09-07 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 22:43 Jay Freyensee [this message]
2016-09-08 9:55 ` [PATCH] nvme-cli: match treq value names to spec Sagi Grimberg
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=1473288206-16121-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).