From: Christoph Hellwig <hch@infradead.org>
To: Cathy Avery <cavery@redhat.com>
Cc: jejb@linux.vnet.ibm.com, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, haiyangz@microsoft.com,
linux-kernel@vger.kernel.org, hch@infradead.org,
devel@linuxdriverproject.org, dan.carpenter@oracle.com
Subject: Re: [PATCH v2] scsi: storvsc: Add support for FC rport.
Date: Mon, 3 Apr 2017 05:17:18 -0700 [thread overview]
Message-ID: <20170403121718.GA13130@infradead.org> (raw)
In-Reply-To: <1491219195-3692-1-git-send-email-cavery@redhat.com>
> if (host->transportt == fc_transport_template) {
> + struct fc_rport_identifiers ids = {
> + .roles = FC_PORT_ROLE_FCP_TARGET,
> + };
I don't think storvsc ever acts as FCP target.
next prev parent reply other threads:[~2017-04-03 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 11:33 [PATCH v2] scsi: storvsc: Add support for FC rport Cathy Avery
2017-04-03 12:17 ` Christoph Hellwig [this message]
2017-04-03 13:14 ` Cathy Avery
2017-04-04 6:53 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2017-03-17 15:17 Cathy Avery
2017-03-21 18:10 ` KY Srinivasan
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=20170403121718.GA13130@infradead.org \
--to=hch@infradead.org \
--cc=cavery@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jejb@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox