From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 1/7] nvme-fabrics: Add FC transport FC-NVME definitions
Date: Tue, 4 Oct 2016 09:32:39 +0200 [thread overview]
Message-ID: <60438ee8-66d4-4730-fed3-470a12bfa9a1@suse.de> (raw)
In-Reply-To: <57f34bb1.R7Xz9kkZOAJuQODz%james.smart@broadcom.com>
On 10/04/2016 08:26 AM, James Smart wrote:
>
> nvme-fabrics: Add FC transport FC-NVME definitions:
> - Formats for Cmd, Data, Rsp IUs
> - Formats FC-4 LS definitions
>
> (Patch unchanged from prior posting)
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
> Acked-by: Johannes Thumshirn <jth at kernel.org>
> Acked-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
> Reviewed-by: Christoph Hellwig <hch at lst.de>
> ---
> include/linux/nvme-fc.h | 296 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 296 insertions(+)
> create mode 100644 include/linux/nvme-fc.h
>
I would have loved to use the SCSI FC headers here; eg the definitions
for FC-LS are most definitely duplicated.
But until we've sorted that one out:
Reviewed-by: Hannes Reinecke <hare at suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare at suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: J. Hawn, J. Guild, F. Imend?rffer, HRB 16746 (AG N?rnberg)
next prev parent reply other threads:[~2016-10-04 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 6:26 [PATCH 1/7] nvme-fabrics: Add FC transport FC-NVME definitions James Smart
2016-10-04 7:32 ` Hannes Reinecke [this message]
2016-10-04 13:58 ` Christoph Hellwig
2016-10-05 6:29 ` Sagi Grimberg
2016-10-05 23:21 ` James Smart
2016-10-06 6:31 ` Hannes Reinecke
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=60438ee8-66d4-4730-fed3-470a12bfa9a1@suse.de \
--to=hare@suse.de \
/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