From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH] nvme-cli: match treq value names to spec
Date: Thu, 8 Sep 2016 12:55:04 +0300 [thread overview]
Message-ID: <09eb5c3f-f952-aa91-abac-f3f30c100aa5@grimberg.me> (raw)
In-Reply-To: <1473288206-16121-1-git-send-email-james_p_freyensee@linux.intel.com>
Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
prev parent reply other threads:[~2016-09-08 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 22:43 [PATCH] nvme-cli: match treq value names to spec Jay Freyensee
2016-09-08 9:55 ` Sagi Grimberg [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=09eb5c3f-f952-aa91-abac-f3f30c100aa5@grimberg.me \
--to=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).