From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH v3 0/7] nvme-fabrics: Add FC-NVME Transport support
Date: Tue, 25 Oct 2016 18:49:50 +0300 [thread overview]
Message-ID: <8463b882-2fd6-0e32-a58f-ef53148775a7@grimberg.me> (raw)
In-Reply-To: <df4b85dd-9e7b-12dd-5f54-2f8f13c28ba6@grimberg.me>
Oh, I see you didn't include review tags with the
new series...
What are the revision changes? (so I can track down
review tags)
Alternatively, if you want a fresh look from everyone
perhaps people can re-add their review tags?
prev parent reply other threads:[~2016-10-25 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 19:31 [PATCH v3 0/7] nvme-fabrics: Add FC-NVME Transport support James Smart
2016-10-25 15:47 ` Sagi Grimberg
2016-10-25 15:49 ` 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=8463b882-2fd6-0e32-a58f-ef53148775a7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.