From: Stelian Pop <stelian@popies.net>
To: Andries.Brouwer@cwi.nl
Cc: James.Bottomley@steeleye.com, stern@rowland.harvard.edu,
afafc@rnl.ist.utl.pt, greg@kroah.com, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, mike@hingston.demon.co.uk,
pwkpete@yahoo.com
Subject: Re: [example PATCH - not for applying] exclude certain commands
Date: Thu, 24 Apr 2003 23:33:55 +0200 [thread overview]
Message-ID: <20030424213355.GA1277@deep-space-9.dsnet> (raw)
In-Reply-To: <UTC200304241521.h3OFL7e14246.aeb@smtp.cwi.nl>
On Thu, Apr 24, 2003 at 05:21:07PM +0200, Andries.Brouwer@cwi.nl wrote:
> That is good. But there is one point I do not understand.
> Stelian Pop reports on two devices, both US_SC_UFI.
> But usb_stor_ufi_command() already contained code to
> make the length 8. How can it be that my sd.c change
> improved things?
Good question.
Could it be that the unusual_devs treatment is flawed somewhere ?
I'll enable debug traces in usb-storage tomorrow again and try to
trace this a bit more. If there is something more specific I need
to look at just tell me.
> Can it be that earlier tests were for 2.5.67 and later tests
> for 2.5.68, and Matt's improvements of the latter over the former
> are the real reason of improved behaviour?
No. I've done all tests (both without - resulting in failures - and
with the sd.c patch) with the latest 2.5 bk tree as of this morning.
The sd.c patch *is* needed to make it work.
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2003-04-24 21:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 15:21 [example PATCH - not for applying] exclude certain commands Andries.Brouwer
2003-04-24 15:56 ` Pete
2003-04-24 21:33 ` Stelian Pop [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-27 2:29 Andries.Brouwer
2003-04-27 4:32 ` James Bottomley
2003-04-26 21:44 Andries.Brouwer
2003-04-26 22:13 ` Matthew Dharm
2003-04-26 22:43 ` James Bottomley
2003-04-27 1:34 ` Matthew Dharm
2003-04-27 2:15 ` James Bottomley
2003-04-27 9:35 ` Matthew Dharm
2003-04-27 15:41 ` James Bottomley
2003-04-27 18:52 ` Kai Makisara
2003-04-27 19:52 ` Matthew Dharm
2003-04-28 19:05 ` Luben Tuikov
2003-04-28 19:12 ` Luben Tuikov
2003-04-28 20:19 ` Matthew Dharm
2003-04-28 21:33 ` Luben Tuikov
2003-04-26 22:29 ` James Bottomley
2003-04-27 0:24 ` Patrick Mansfield
2003-04-27 1:39 ` Matthew Dharm
2003-04-25 0:43 Andries.Brouwer
2003-04-25 2:12 ` Matthew Dharm
2003-04-25 14:32 ` Alan Stern
2003-04-25 15:12 ` Oliver Neukum
2003-04-26 0:58 ` Alan Stern
2003-04-26 8:24 ` Oliver Neukum
2003-04-26 15:22 ` Alan Stern
2003-04-24 18:59 Andries.Brouwer
2003-04-24 19:14 ` Matthew Dharm
2003-04-24 20:20 ` James Bottomley
2003-04-24 20:59 ` Matthew Dharm
2003-04-24 21:43 ` Patrick Mansfield
2003-04-24 9:46 Andries.Brouwer
2003-04-24 9:56 ` Stelian Pop
2003-04-24 14:05 ` Alan Stern
2003-04-24 14:26 ` James Bottomley
2003-04-24 14:46 ` Alan Stern
2003-04-24 15:26 ` James Bottomley
2003-04-24 9:08 Andries.Brouwer
2003-04-24 18:22 ` Matthew Dharm
2003-04-23 22:39 Andries.Brouwer
2003-04-24 0:10 ` Matthew Dharm
2003-04-24 8:05 ` André Cruz
2003-04-24 9:15 ` Stelian Pop
2003-04-24 9:22 ` Stelian Pop
2003-04-24 11:45 ` Mike Bursell
2003-04-24 12:44 ` 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=20030424213355.GA1277@deep-space-9.dsnet \
--to=stelian@popies.net \
--cc=Andries.Brouwer@cwi.nl \
--cc=James.Bottomley@steeleye.com \
--cc=afafc@rnl.ist.utl.pt \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mike@hingston.demon.co.uk \
--cc=pwkpete@yahoo.com \
--cc=stern@rowland.harvard.edu \
/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