linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: "michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 4/6] lpfc: use SCSI_MLQUEUE_TARGET_BUSY when catching the rport transition race
Date: Tue, 19 Aug 2008 11:27:09 -0400	[thread overview]
Message-ID: <48AAE64D.9010000@emulex.com> (raw)
In-Reply-To: <1219004683-6468-5-git-send-email-michaelc@cs.wisc.edu>

Ack

-- james s

michaelc@cs.wisc.edu wrote:
> From: Mike Christie <michaelc@cs.wisc.edu>
> 
> We do want to call right back into the queuecommand during the race,
> so we can just use SCSI_MLQUEUE_TARGET_BUSY.
> 
> Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
> Cc: James Smart <James.Smart@Emulex.Com>
> 
> ---
>  drivers/scsi/lpfc/lpfc_scsi.c |    9 +++++----
>  1 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/scsi/lpfc/lpfc_scsi.c b/drivers/scsi/lpfc/lpfc_scsi.c

  parent reply	other threads:[~2008-08-19 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 20:24 allow scsi-ml to manage target queueing limits (v3) michaelc
2008-08-17 20:24 ` [PATCH 1/6] scsi: Add helper code so transport classes/driver can control queueing (take 3) michaelc
2008-08-17 20:24   ` [PATCH 2/6] qla4xxx: return SCSI_MLQUEUE_TARGET_BUSY when driver has detected session error michaelc
2008-08-17 20:24     ` [PATCH 3/6] qla2xxx: return SCSI_MLQUEUE_TARGET_BUSY when driver has detected rport error or race michaelc
2008-08-17 20:24       ` [PATCH 4/6] lpfc: use SCSI_MLQUEUE_TARGET_BUSY when catching the rport transition race michaelc
2008-08-17 20:24         ` [PATCH 5/6] mptfc: " michaelc
2008-08-17 20:24           ` [PATCH 6/6] libiscsi: Use SCSI_MLQUEUE_TARGET_BUSY michaelc
2008-08-19 15:27         ` James Smart [this message]
2008-08-19 16:16       ` [PATCH 3/6] qla2xxx: return SCSI_MLQUEUE_TARGET_BUSY when driver has detected rport error or race Andrew Vasquez

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=48AAE64D.9010000@emulex.com \
    --to=james.smart@emulex.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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).