From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
mdharm-usb@one-eyed-alien.net,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
usb-storage@lists.one-eyed-alien.net
Subject: Re: adding flag for 192 byte mode sense
Date: 22 Mar 2004 11:31:44 -0500 [thread overview]
Message-ID: <1079973105.2072.42.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0403221105290.8035-100000@ida.rowland.org>
On Mon, 2004-03-22 at 11:16, Alan Stern wrote:
> Do they look good? Should they be applied? One suggestion for a change:
> the flag could be renamed "use_192_bytes_for_ms" since we may end up
> wanting to use it for both page 0x3f and 0x08.
They already are in the scsi-misc-2.6 repository.
> 3. When a USB mass storage device enters a state that requires a
> device reset, what command completion code should the usb-storage driver
> return to invoke the SCSI error handler? And is there any way to do this
> so that the error handler skips the initial TEST UNIT READY step and goes
> directly to the device reset?
Anything that maps to FAILED in scsi_decide_disposition()
What TEST UNIT READY? The error handler only issues those *after*
recovery, not before.
James
next prev parent reply other threads:[~2004-03-22 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 1:46 adding flag for 192 byte mode sense Patrick Mansfield
2004-03-14 1:49 ` [PATCH] Replace scsi_host flags with scsi_device sdev_bflags Patrick Mansfield
2004-03-14 1:50 ` [PATCH] Add 192 byte MODE SENSE flag Patrick Mansfield
2004-03-16 17:25 ` adding flag for 192 byte mode sense Alan Stern
2004-03-16 18:02 ` Matthew Dharm
2004-03-16 20:08 ` Alan Stern
2004-03-16 20:27 ` [usb-storage] " Pat LaVarre
2004-03-22 16:16 ` Alan Stern
2004-03-22 16:31 ` James Bottomley [this message]
2004-03-22 17:28 ` Alan Stern
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=1079973105.2072.42.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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