All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Bob Frey <bfrey@turbolinux.com.cn>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: scsi_scan problem.
Date: Thu, 15 Mar 2001 00:19:15 -0500	[thread overview]
Message-ID: <3AB050D3.15AF5EF1@redhat.com> (raw)
In-Reply-To: <3AB028BE.E8940EE6@redhat.com> <20010314213543.A30816@devserv.devel.redhat.com> <20010315130641.A14138@bfrey.dev.cn.tlan>

Bob Frey wrote:
> 
> On Wed, Mar 14, 2001 at 09:35:43PM -0500, Pete Zaitcev wrote:
> > 16384 LUNs for Fibre Channel. As you see, scanning is out of the
> > question. You must issue REPORT LUNs and fall back on scanning
> > if the device reports a check condition. I did that when I worked
> Why wait for a check condition? There's an INQUIRY field bit that
> indicates whether REPORT LUNs is supported.

And I'm all for using it in the 2.5 kernel SCSI stack ;-)

-- 

 Doug Ledford <dledford@redhat.com>  http://people.redhat.com/dledford
      Please check my web site for aic7xxx updates/answers before
                      e-mailing me about problems

  reply	other threads:[~2001-03-15  5:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  2:28 scsi_scan problem Doug Ledford
2001-03-15  2:35 ` Pete Zaitcev
2001-03-15  3:03   ` Doug Ledford
2001-03-15  3:09     ` Doug Ledford
2001-03-16 16:53     ` Ishikawa
2001-03-16 19:33       ` Doug Ledford
2001-03-16 20:10         ` Peter Rival
2001-03-17  2:08         ` Ishikawa
2001-03-15  5:06   ` Bob Frey
2001-03-15  5:19     ` Doug Ledford [this message]
2001-03-16 22:39 ` Rafael E. Herrera
2001-03-16 22:54   ` Doug Ledford
2001-03-16 23:40   ` Khalid Aziz
2001-03-17  0:12   ` Patrick Mansfield
2001-03-17  1:56     ` Doug Ledford
2001-03-17  3:37     ` Rafael E. Herrera

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=3AB050D3.15AF5EF1@redhat.com \
    --to=dledford@redhat.com \
    --cc=bfrey@turbolinux.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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.