From: James Bottomley <James.Bottomley@steeleye.com>
To: "Dupuis, Chad" <chad.dupuis@hp.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: patch for scsi_devinfo.c
Date: 21 Jun 2004 15:15:09 -0500 [thread overview]
Message-ID: <1087848910.2079.80.camel@mulgrave> (raw)
In-Reply-To: <A8B003DDA3332A479C0ECCA641F47E6503BE69F9@tayexc13.americas.cpqcorp.net>
On Mon, 2004-06-21 at 15:07, Dupuis, Chad wrote:
> The entries for HP and Compaq HSV110 are incorrect. The HSV110
> controllers report themselves as SCSI 2 devices and therefore need the
> BLIST_LARGELUN flag to see LUNs passed 7.
Do they also respond to REPORT LUNS? In which case we could flag them
as that instead of BLIST_SPARSELUN|BLIST_LARGELUN
James
next prev parent reply other threads:[~2004-06-21 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 20:07 patch for scsi_devinfo.c Dupuis, Chad
2004-06-21 20:15 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 20:16 Dupuis, Chad
2004-06-21 20:23 ` James Bottomley
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=1087848910.2079.80.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=chad.dupuis@hp.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;
as well as URLs for NNTP newsgroup(s).