From: Cathy Avery <cavery@redhat.com>
To: kys@microsoft.com, haiyangz@microsoft.com,
jejb@linux.vnet.ibm.com, martin.petersen@oracle.com
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: [PATCH 0/2] scsi: Create a lightweight FC Transport option for Virtual FC Hosts.
Date: Wed, 18 Jan 2017 15:28:56 -0500 [thread overview]
Message-ID: <1484771338-8903-1-git-send-email-cavery@redhat.com> (raw)
Currently virtual FC hosts or lightweight hosts are not able to be
manually scanned via sysfs due to the fact that they do not
contain the complete characteristic set associated with a normal FC host
( missing rports, vports, etc ) and are not consistent with the current FC
transport model.
Patch 1: The patch provides a lightweight option to the current FC
transport class. The new option is selected by a driver when it
indicates it wants the lightweight transport in fc_function_template.
Patch 2: storvsc elects using the new lightweight FC host option.
Cathy Avery (2):
scsi: scsi_transport_fc: Provide a lightweight option for Virtual FC
Hosts.
scsi: storvsc: Add support for FC lightweight host.
drivers/scsi/scsi_transport_fc.c | 125 +++++++++++++++++++++++++++++++++++++--
drivers/scsi/storvsc_drv.c | 6 +-
include/scsi/scsi_transport_fc.h | 1 +
3 files changed, 123 insertions(+), 9 deletions(-)
--
2.5.0
next reply other threads:[~2017-01-18 20:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 20:28 Cathy Avery [this message]
2017-01-18 20:28 ` [PATCH 1/2] scsi: scsi_transport_fc: Provide a lightweight option for Virtual FC Hosts Cathy Avery
2017-01-19 15:11 ` Christoph Hellwig
2017-01-19 15:11 ` Christoph Hellwig
2017-01-19 17:59 ` Cathy Avery
2017-01-19 17:59 ` Cathy Avery
2017-01-27 15:45 ` KY Srinivasan
2017-01-27 15:45 ` KY Srinivasan
2017-01-18 20:28 ` [PATCH 2/2] scsi: storvsc: Add support for FC lightweight host Cathy Avery
2017-01-18 23:15 ` Dan Carpenter
2017-01-18 23:15 ` Dan Carpenter
2017-01-19 17:55 ` Cathy Avery
2017-01-19 17:55 ` Cathy Avery
2017-01-20 9:31 ` Dan Carpenter
2017-01-20 9:31 ` Dan Carpenter
2017-01-22 18:51 ` Cathy Avery
2017-01-22 18:51 ` Cathy Avery
2017-01-22 19:24 ` Dan Carpenter
2017-01-23 3:13 ` Fam Zheng
2017-01-23 3:13 ` Fam Zheng
2017-01-23 20:55 ` Cathy Avery
2017-01-23 20:55 ` 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=1484771338-8903-1-git-send-email-cavery@redhat.com \
--to=cavery@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.