From: Phil Dibowitz <phil@ipom.com>
To: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org
Subject: Re: Avoid I/O errors when issuing SCSI ioctls to JMicron USB/ATA bridge
Date: Tue, 14 Oct 2008 21:29:59 +0200 [thread overview]
Message-ID: <48F4F337.8080104@ipom.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0810141111080.2662-300000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
Alexandre Oliva wrote:
> Here's the patch that implements the fix you suggested to avoid the
> I/O errors that I was running into with my new USB enclosure with a
> JMicron USB/ATA bridge, while issuing scsi-io USN or other such
> queries used by Fedora's mkinitrd.
> http://bugzilla.kernel.org/show_bug.cgi?id=9638#c85
Alexandre,
The patch looks generally good, but you've included every possible revision
of the hardware. Can you please change your patch to include just the
revision in question (0x0100) rather than the whole range (0x0000 - 0x9999)?
Thanks.
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next parent reply other threads:[~2008-10-14 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0810141111080.2662-300000@iolanthe.rowland.org>
2008-10-14 19:29 ` Phil Dibowitz [this message]
2008-10-19 4:11 ` Avoid I/O errors when issuing SCSI ioctls to JMicron USB/ATA bridge Alexandre Oliva
2008-10-08 23:19 Alexandre Oliva
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=48F4F337.8080104@ipom.com \
--to=phil@ipom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliva@lsd.ic.unicamp.br \
--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