From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 11/15] lpfc 8.2.8 : Update driver to use new Host byte error code DID_TRANSPORT_DISRUPTED
Date: Thu, 04 Sep 2008 16:08:18 -0500 [thread overview]
Message-ID: <1220562498.3276.60.camel@localhost.localdomain> (raw)
In-Reply-To: <1219629018.7890.41.camel@localhost.localdomain>
On Sun, 2008-08-24 at 21:50 -0400, James Smart wrote:
> Update driver to use new Host byte error code DID_TRANSPORT_DISRUPTED.
>
> This patch depends pending upstream patches described in:
> http://marc.info/?l=linux-scsi&m=121263014808604&w=2
>
> Particularly:
> http://marc.info/?l=linux-scsi&m=121263014908607&w=2
> which defines DID_TRANSPORT_DISRUPTED.
>
> This patch supercedes the lpfc patch in that series:
> http://marc.info/?l=linux-scsi&m=121263015008616&w=2
I've got this one, but only partially. The third hunk doesn't apply:
--- 1072,1078 ----
* transport is still transitioning.
*/
if (!ndlp || !NLP_CHK_NODE_ACT(ndlp)) {
+ cmnd->result = ScsiResult(DID_TRANSPORT_DISRUPTED, 0);
goto out_fail_command;
}
It became a goto out_target_busy, which returns SCSI_MLQUEUE_TARGET_BUSY
via a patch which you acked.
James
next prev parent reply other threads:[~2008-09-04 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 1:50 [PATCH 11/15] lpfc 8.2.8 : Update driver to use new Host byte error code DID_TRANSPORT_DISRUPTED James Smart
2008-09-04 21:08 ` James Bottomley [this message]
2008-09-05 14:30 ` Mike Christie
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=1220562498.3276.60.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=James.Smart@Emulex.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