From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH] Add fc transport support to nvmetcli
Date: Thu, 20 Apr 2017 13:23:47 +0300 [thread overview]
Message-ID: <f7de0341-2ac6-2666-93ac-d3489e03c59c@grimberg.me> (raw)
In-Reply-To: <20170412230914.23788-1-jsmart2021@gmail.com>
Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
prev parent reply other threads:[~2017-04-20 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 23:09 [PATCH] Add fc transport support to nvmetcli jsmart2021
2017-04-18 8:03 ` Christoph Hellwig
2017-04-20 10:23 ` 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=f7de0341-2ac6-2666-93ac-d3489e03c59c@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).