From: Jeff Garzik <jeff@garzik.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH v2] libata: Simulate REPORT LUNS for ATAPI devices
Date: Thu, 07 Dec 2006 07:20:54 -0500 [thread overview]
Message-ID: <45780726.8010107@garzik.org> (raw)
In-Reply-To: <4574B004.6030606@us.ibm.com>
Darrick J. Wong wrote:
> The Quantum GoVault SATAPI removable disk device returns ATA_ERR in
> response to a REPORT LUNS packet. If this happens to an ATAPI device
> that is attached to a SAS controller (this is the case with sas_ata),
> the device does not load because SCSI won't touch a "SCSI device"
> that won't report its LUNs. Since most ATAPI devices don't support
> multiple LUNs anyway, we might as well fake a response like we do for
> ATA devices.
>
> Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
Seems sane to me, but I would like additional comment/testing/etc.
before applying...
next prev parent reply other threads:[~2006-12-07 12:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 23:02 libata: Simulate REPORT LUNS for ATAPI devices when not supported Darrick J. Wong
2006-12-04 23:12 ` Jeff Garzik
2006-12-04 23:32 ` [PATCH v2] libata: Simulate REPORT LUNS for ATAPI devices Darrick J. Wong
2006-12-07 12:20 ` Jeff Garzik [this message]
2006-12-07 15:47 ` Douglas Gilbert
2006-12-07 18:09 ` James Bottomley
2006-12-07 19:13 ` Douglas Gilbert
2006-12-11 16:24 ` Jeff Garzik
2006-12-11 16:44 ` James Bottomley
2006-12-11 16:59 ` Jeff Garzik
2006-12-12 22:24 ` Darrick J. Wong
2006-12-13 16:10 ` James Bottomley
2006-12-13 17:38 ` Darrick J. Wong
2006-12-13 17:57 ` James Bottomley
2006-12-13 18:56 ` Patrick Mansfield
2006-12-13 20:06 ` Darrick J. Wong
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=45780726.8010107@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=djwong@us.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).