From: Patrick Mansfield <patmans@us.ibm.com>
To: Kurt Garloff <garloff@suse.de>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/3] Try LUN 1 and use bflags
Date: Fri, 31 Mar 2006 08:39:52 -0800 [thread overview]
Message-ID: <20060331163952.GA22277@us.ibm.com> (raw)
In-Reply-To: <20060329201147.GH7919@tpkurt.suse.de>
On Wed, Mar 29, 2006 at 10:11:47PM +0200, Kurt Garloff wrote:
> @@ -945,11 +945,13 @@ static void scsi_sequential_lun_scan(str
> sparse_lun = 0;
>
> /*
> - * If not sparse lun and no device attached at LUN 0 do not scan
> - * any further.
> - */
> + * If LUN0 did respond, but did not have an attachable LUN (PQ=3),
> + * we do NOT abort the sequential scan yet, let's try one more
> + * LUN and only abort the scan if we don't find anything there.
> + *
> if (!sparse_lun && (lun0_res != SCSI_SCAN_LUN_PRESENT))
> return;
> + */
Just delete all that, and get rid of lun0_res.
-- Patrick Mansfield
next prev parent reply other threads:[~2006-03-31 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 20:10 [PATCH 0/3] SCSI scanning for PQ3 devs Kurt Garloff
2006-03-29 20:11 ` [PATCH 1/3] Try LUN 1 and use bflags Kurt Garloff
2006-03-31 16:39 ` Patrick Mansfield [this message]
2006-03-29 20:12 ` [PATCH 2/3] Better log messages for PQ3 devs Kurt Garloff
2006-03-29 20:30 ` Matthew Wilcox
2006-03-29 22:12 ` Kurt Garloff
2006-03-29 22:23 ` James Bottomley
2006-03-29 20:13 ` [PATCH 3/3] BLIST_ATTACH_PQ3 flags Kurt Garloff
2006-04-03 13:16 ` [PATCH 1/3] Try LUN 1 and use bflags Kurt Garloff
2006-04-03 13:18 ` [PATCH 2/3] Better log messages for PQ3 devs Kurt Garloff
2006-04-03 13:20 ` [PATCH 3/3] BLIST_ATTACH_PQ3 flags Kurt Garloff
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=20060331163952.GA22277@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=garloff@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).