From: J Freyensee <james_p_freyensee@linux.intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
James Smart <james.smart@broadcom.com>
Cc: linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/5] nvme-fabrics: Add FC transport LLDD api definitions
Date: Fri, 29 Jul 2016 15:10:30 -0700 [thread overview]
Message-ID: <1469830230.12212.46.camel@linux.intel.com> (raw)
In-Reply-To: <20160725091253.cq6lpgultbzleyq5@c203.arch.suse.de>
On Mon, 2016-07-25 at 11:12 +0200, Johannes Thumshirn wrote:
> On Fri, Jul 22, 2016 at 05:23:56PM -0700, James Smart wrote:
> >
> > nvme-fabrics: Add FC transport LLDD api definitions:
> >
> > Host:
> > -LLDD registration with the host transport
> > -registering host ports (local ports) and target ports seen on
> > fabric (remote ports)
> > -Data structures and call points for FC-4 LS's and FCP IO requests
> >
> > Target:
> > -LLDD registration with the target transport
> > -registering nvme subsystem ports (target ports)
> > -Data structures and call points for reception of FC-4 LS's and
> > FCP IO requests, and callbacks to perform data and rsp transfers
> > for the io.
> >
> >
> > Signed-off-by: James Smart <james.smart@broadcom.com>
>
> Acked-by: Johannes Thumshirn <jth@kernel.org>
Acked-by: Jay Freyensee <james_p_freyensee@linux.intel.com>
>
next prev parent reply other threads:[~2016-07-29 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 0:23 [PATCH 2/5] nvme-fabrics: Add FC transport LLDD api definitions James Smart
2016-07-25 9:12 ` Johannes Thumshirn
2016-07-29 22:10 ` J Freyensee [this message]
2016-08-11 21:06 ` Christoph Hellwig
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=1469830230.12212.46.camel@linux.intel.com \
--to=james_p_freyensee@linux.intel.com \
--cc=james.smart@broadcom.com \
--cc=jthumshirn@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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).