From: Doug Ledford <dledford@redhat.com>
To: "Rafael E. Herrera" <raffo@neuronet.pitt.edu>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: scsi_scan problem.
Date: Fri, 16 Mar 2001 17:54:07 -0500 [thread overview]
Message-ID: <3AB2998F.EC58C3E5@redhat.com> (raw)
In-Reply-To: <3AB028BE.E8940EE6@redhat.com> <3AB29636.64C90827@neuronet.pitt.edu>
"Rafael E. Herrera" wrote:
>
> I applied the first hunk to version 2.4.3-pre4, as by email with Doug.
> The output for the scsi devices follows and is identical with and
> without the patch.
Thank you Rafael. This is what I suspected. I'm not sure when we starting
considering devices with a peripheral qualifier of 1 as being valid, but I
suspect it happened when the scsi_scan.c code was separated out of scsi.c. In
any case, I'm pretty positive that it is the wrong thing to do. This report
at least alleviates one of my fears about broken device possibilities and
starts to confirm my position.
> Maybe someone can explain the meaning of the illegal
> requests at the end. Nevertheless, I can use the drive fine.
As to the illegal request messages, I'm not sure what those are about ;-)
--
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
next prev parent reply other threads:[~2001-03-16 22:49 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
2001-03-16 22:39 ` Rafael E. Herrera
2001-03-16 22:54 ` Doug Ledford [this message]
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=3AB2998F.EC58C3E5@redhat.com \
--to=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=raffo@neuronet.pitt.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