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 3/9] lpfc: Devices are not discovered during takeaway/giveback testing
Date: Sun, 24 May 2015 21:56:43 +0200 [thread overview]
Message-ID: <20150524215643.00003055@localhost> (raw)
In-Reply-To: <555f405d.19aP4Ju4SItrRE4D%james.smart@avagotech.com>
James Smart wrote:
>
> Devices are not discovered during takeaway/giveback testing
>
> When a remote nport changes it's DID, a new ndlp is used.
its
> However, we left the old ndlp state unchanged and still in
> a discovery state. The may stall discovery resulting in some
The?
> devices not being discovered. Correct by swapping the state
two spaces
> of the 2 ndlp's when a DID swap is detected.
Sebastian
next prev parent reply other threads:[~2015-05-24 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 14:42 [PATCH 3/9] lpfc: Devices are not discovered during takeaway/giveback testing James Smart
2015-05-24 19:56 ` Sebastian Herbszt [this message]
2015-05-26 13:36 ` James Smart
2015-05-25 15:15 ` Hannes Reinecke
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=20150524215643.00003055@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox