From: Robert Love <robert.w.love@intel.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: "devel@open-fcoe.org" <devel@open-fcoe.org>,
Joe Eykholt <jeykholt@cisco.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] thaw FC local port
Date: Thu, 16 Dec 2010 15:18:41 -0800 [thread overview]
Message-ID: <1292541521.1346.20.camel@fritz> (raw)
In-Reply-To: <AANLkTi=4waDVnmLg9VRvrwRej+TLe4KGsL58XdWdG091@mail.gmail.com>
On Thu, 2010-12-16 at 08:07 -0800, Hillf Danton wrote:
> The state machine of local port is freezed if it could not get ready,
> so thawing is necessary.
>
Please start putting a prefix "fcoe: ", "libfc: " or "libfcoe: " on your
patch titles. Also, please provide more meaningful commit messages. I
believe that I've pointed out these two issues with your patches before.
> Signed-off-by: Hillf Danton <dhillf@gmail.com>
> ---
>
> --- a/drivers/scsi/libfc/fc_lport.c 2010-11-01 19:54:12.000000000 +0800
> +++ b/drivers/scsi/libfc/fc_lport.c 2010-12-17 00:08:06.000000000 +0800
> @@ -1514,11 +1514,11 @@ void fc_lport_enter_flogi(struct fc_lpor
>
> fc_lport_state_enter(lport, LPORT_ST_FLOGI);
>
> - if (lport->point_to_multipoint) {
> - if (lport->port_id)
> + if (lport->point_to_multipoint)
> + if (lport->port_id) {
> fc_lport_enter_ready(lport);
> - return;
> - }
> + return;
> + }
>
> fp = fc_frame_alloc(lport, sizeof(struct fc_els_flogi));
> if (!fp)
We do not want to proceed with sending a FLOGI here when we're in
point-to-multipoint (VN2VN) mode. VN2VN is a mode where there is no
fabric and we FLOGI directly into the remote port. So for VN2VN the
FLOGI happens in the rport layer.
//Rob
next prev parent reply other threads:[~2010-12-16 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 16:07 [PATCH] thaw FC local port Hillf Danton
2010-12-16 23:18 ` Robert Love [this message]
2010-12-17 13:46 ` Hillf Danton
2010-12-17 19:04 ` Robert Love
2010-12-18 13:20 ` Hillf Danton
2010-12-17 19:33 ` Joe Eykholt
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=1292541521.1346.20.camel@fritz \
--to=robert.w.love@intel.com \
--cc=devel@open-fcoe.org \
--cc=dhillf@gmail.com \
--cc=jeykholt@cisco.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