From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 1/3] nvme-fabrics: patch target code in prep for FC transport support
Date: Mon, 26 Sep 2016 08:02:52 -0700 [thread overview]
Message-ID: <20160926150251.GB9220@infradead.org> (raw)
In-Reply-To: <57e93218.4CgczdRxtAdq+zwV%james.smart@broadcom.com>
On Mon, Sep 26, 2016@07:35:04AM -0700, James Smart wrote:
>
> Patch nvme-fabrics target code in prep for FC transport support:
> - Add FC transport type decoding
> - Add FC address family decoding
>
> (Patch unchanged from prior posting)
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
> Acked-by: Johannes Thumshirn <jth at kernel.org>
> Reviewed-by: Christoph Hellwig <hch at lst.de>
Looks sensible, we'll queue this up once the rest of the FC support
is ready.
prev parent reply other threads:[~2016-09-26 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 14:35 [PATCH 1/3] nvme-fabrics: patch target code in prep for FC transport support James Smart
2016-09-26 15:02 ` Christoph Hellwig [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=20160926150251.GB9220@infradead.org \
--to=hch@infradead.org \
/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).