From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 1/5] nvme-fabrics: Add FC transport FC-NVME definitions
Date: Tue, 16 Aug 2016 13:01:56 +0300 [thread overview]
Message-ID: <4bdd75e3-806a-4fae-3ef8-4d52b145b83f@grimberg.me> (raw)
In-Reply-To: <20160811210349.GD18013@infradead.org>
> Looks fine,
>
> Reviewed-by: Christoph Hellwig <hch at lst.de>
Hey James,
Can you collect review tags, address CR comments and resend the series?
I'd like to stage these for 0-day testing and try to get it into 4.9.
Thanks,
Sagi.
next prev parent reply other threads:[~2016-08-16 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 0:23 [PATCH 1/5] nvme-fabrics: Add FC transport FC-NVME definitions James Smart
2016-07-25 8:56 ` Johannes Thumshirn
2016-07-29 22:10 ` J Freyensee
2016-08-11 21:03 ` Christoph Hellwig
2016-08-16 10:01 ` Sagi Grimberg [this message]
2016-08-16 16:31 ` James Smart
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=4bdd75e3-806a-4fae-3ef8-4d52b145b83f@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).