From: Cathy Avery <cavery@redhat.com>
To: kys@microsoft.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, hch@infradead.org
Cc: sthemmin@microsoft.com, haiyangz@microsoft.com,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: [PATCH v3 0/2] scsi: storvsc: Add support for FC rport
Date: Mon, 17 Apr 2017 14:37:44 -0400 [thread overview]
Message-ID: <1492454266-24587-1-git-send-email-cavery@redhat.com> (raw)
The updated patch set provides a way for drivers ( specifically
storvsc in this case ) that expose virturalized fc devices
but that do not expose rports to be manually scanned. This is
done via creating a pseudo rport in storvsc and a
corresponding dummy initiator rport role in the fc transport.
Changes since v2:
- Additional patch adding FC_PORT_ROLE_FCP_DUMMY_INITIATOR role
to fc_transport
- Changed storvsc rport role to FC_PORT_ROLE_FCP_DUMMY_INITIATOR
Changes since v1:
- Fix fc_rport_identifiers init [Stephen Hemminger]
- Better error checking
Cathy Avery (2):
scsi: scsi_transport_fc: Add dummy initiator role to rport
scsi: storvsc: Add support for FC rport.
drivers/scsi/scsi_transport_fc.c | 10 ++++++----
drivers/scsi/storvsc_drv.c | 23 ++++++++++++++++++-----
include/scsi/scsi_transport_fc.h | 1 +
3 files changed, 25 insertions(+), 9 deletions(-)
--
2.5.0
next reply other threads:[~2017-04-17 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 18:37 Cathy Avery [this message]
2017-04-17 18:37 ` [PATCH v3 1/2] scsi: scsi_transport_fc: Add dummy initiator role to rport Cathy Avery
2017-04-19 6:46 ` Christoph Hellwig
2017-04-17 18:37 ` [PATCH v3 2/2] scsi: storvsc: Add support for FC rport Cathy Avery
2017-04-19 6:47 ` Christoph Hellwig
2017-04-19 23:14 ` [PATCH v3 0/2] " Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2017-04-05 18:45 Cathy Avery
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=1492454266-24587-1-git-send-email-cavery@redhat.com \
--to=cavery@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sthemmin@microsoft.com \
/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).