From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: linux-scsi@vger.kernel.org, duane.grigsby@qlogic.com
Subject: Re: [PATCH] FC Transport support for vports based on NPIV
Date: Tue, 22 May 2007 12:40:08 +0200 [thread overview]
Message-ID: <20070522104007.GA21345@schmichrtp> (raw)
In-Reply-To: <4651BE89.7020200@emulex.com>
On Mon, May 21, 2007 at 11:45:13AM -0400, James Smart wrote:
> True - so this means that who-ever is setting the subchannel device
> permanent_port_name value needs to take into account this conversation,
> when T11.3 actually makes a choice on what it should be.
I will keep this in mind. Probably this would involve the FCP adapter
and the reporting in zfcp.
Anyway, my main goal was to understand the changes in the FC transport
class and the possible impact to zfcp. Thanks for the clarification
of my questions.
Christof
prev parent reply other threads:[~2007-05-22 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 20:01 [PATCH] FC Transport support for vports based on NPIV James Smart
2007-05-12 15:02 ` Christoph Hellwig
2007-05-14 12:12 ` Christof Schmitt
2007-05-14 15:56 ` ` James Smart
2007-05-14 15:57 ` [PATCH] FC Transport support for vports based on NPIV James Smart
2007-05-21 15:27 ` Christof Schmitt
2007-05-21 15:45 ` James Smart
2007-05-22 10:40 ` Christof Schmitt [this message]
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=20070522104007.GA21345@schmichrtp \
--to=christof.schmitt@de.ibm.com \
--cc=James.Smart@Emulex.Com \
--cc=duane.grigsby@qlogic.com \
--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).