From: James Bottomley <James.Bottomley@SteelEye.com>
To: "conway, heather" <conway_heather@emc.com>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: Request to add EMC Invista to the v2.6.x SCSI Blacklist...
Date: Sat, 30 Jul 2005 10:00:24 -0500 [thread overview]
Message-ID: <1122735625.5055.3.camel@mulgrave> (raw)
In-Reply-To: <FA2F59D0E55B4B4892EA076FF8704F5509DDC7A5@srgraham.eng.emc.com>
On Wed, 2005-07-27 at 10:22 -0400, conway, heather wrote:
> I'd like to request that the enclosed patch to scsi_devinfo.c be considered
> for inclusion in the v2.6.x kernel. This would add support for sparse LUNs
> and large LUNs for the EMC Invista product.
For 2.6, I assume this device reports compliance with SCSI-2; could you
check to see if it would actually supports the REPORT_LUNS command? If
it does, the blacklist entry would be BLIST_REPORTLUN2; if not, then
I'll put in what you sent.
Thanks,
James
next prev parent reply other threads:[~2005-07-30 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 14:22 Request to add EMC Invista to the v2.6.x SCSI Blacklist conway, heather
2005-07-30 15:00 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 15:45 conway, heather
2005-08-11 16:39 ` James Bottomley
2005-08-15 20:33 conway, heather
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=1122735625.5055.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=conway_heather@emc.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