From: Sebastian Herbszt <herbszt@gmx.de>
To: James Smart <james.smart@avagotech.com>
Cc: linux-scsi@vger.kernel.org, Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [PATCH v2 01/15] lpfc: The lpfc driver does not issue RFF_ID and RFT_ID in the correct sequence
Date: Sun, 24 May 2015 13:27:48 +0200 [thread overview]
Message-ID: <20150524132748.00006243@localhost> (raw)
In-Reply-To: <555e1c04.iUZP5CxxteUR0DUk%james.smart@avagotech.com>
James Smart wrote:
>
> The lpfc driver does not issue RFF_ID and RFT_ID in the correct sequence
>
> Signed-off-by: Dick Kennedy <dick.kennedy@avagotech.com>
> Signed-off-by: James Smart <james.smart@avagotech.com>
> ---
> drivers/scsi/lpfc/lpfc_hbadisc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/lpfc/lpfc_hbadisc.c b/drivers/scsi/lpfc/lpfc_hbadisc.c
> index 2500f15..f2db89f 100644
> --- a/drivers/scsi/lpfc/lpfc_hbadisc.c
> +++ b/drivers/scsi/lpfc/lpfc_hbadisc.c
> @@ -3868,11 +3868,11 @@ out:
>
> if (vport->port_state < LPFC_VPORT_READY) {
> /* Link up discovery requires Fabric registration. */
> - lpfc_ns_cmd(vport, SLI_CTNS_RFF_ID, 0, 0); /* Do this first! */
> lpfc_ns_cmd(vport, SLI_CTNS_RNN_ID, 0, 0);
> lpfc_ns_cmd(vport, SLI_CTNS_RSNN_NN, 0, 0);
> lpfc_ns_cmd(vport, SLI_CTNS_RSPN_ID, 0, 0);
> lpfc_ns_cmd(vport, SLI_CTNS_RFT_ID, 0, 0);
> + lpfc_ns_cmd(vport, SLI_CTNS_RFF_ID, 0, 0);
>
> /* Issue SCR just before NameServer GID_FT Query */
> lpfc_issue_els_scr(vport, SCR_DID, 0);
Reviewed-by: Sebastian Herbszt <herbszt@gmx.de>
Sebastian
prev parent reply other threads:[~2015-05-24 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 17:55 [PATCH v2 01/15] lpfc: The lpfc driver does not issue RFF_ID and RFT_ID in the correct sequence James Smart
2015-05-24 11:27 ` Sebastian Herbszt [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=20150524132748.00006243@localhost \
--to=herbszt@gmx.de \
--cc=james.smart@avagotech.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 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.