content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: RE: cciss updates [1 of 2]
Date: Thu, 25 Mar 2004 12:55:15 -0600
Message-ID: <D4CFB69C345C394284E4B78B876C1CF105BC1F61@cceexc23.americas.cpqcorp.net>
Thread-Topic: cciss updates [1 of 2]
Thread-Index: AcQShHL/sJGM69cuTyi4RuIv/Rr3cAAFhkuQ
From: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: <axboe@suse.de>, <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1042
Lines: 31

Yep, that would the right thing to do. But right now management wants this :(

-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Thursday, March 25, 2004 10:14 AM
To: Miller, Mike (OS Dev)
Cc: axboe@suse.de; linux-kernel@vger.kernel.org
Subject: Re: cciss updates [1 of 2]


mikem@beardog.cca.cpqcorp.net wrote:
> Please consider this change for inclusion in the 2.4 kernel.
> 
> This change is required to support the new MSA30 storage enclosure.
> If you do a SCSI inquiry to a SATA disk bad things happen. This patch prevents 
> the inquiry from going to SATA disks.


I 'ack' both of those patches, but am still curious:  wouldn't you want 
to either (a) simulate an inquiry page via ATA's identify device or (b) 
allow userspace to issue identify device?

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/