public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Soeren Sonnenburg <kernel@nn7.de>
Subject: Re: [linux-usb-devel] 2.6.20-rc6 SCSI error: I/O error - trouble with mass storage devices ?!
Date: Tue, 30 Jan 2007 17:12:54 -0600	[thread overview]
Message-ID: <45BFD0F6.9040201@shaw.ca> (raw)
In-Reply-To: <fa.SlST1aKbNgZSghdvI9esD81kVnI@ifi.uio.no>

Alan Stern wrote:

> The log revealed that the phone's firmware returns garbage values in the 
> Residue field for some WRITEs.  This patch should take care of it.
> 
> Alan Stern

Is it just me, or should some of these device quirk entries that keep 
being added be made unconditional? Adding entries for every single 
device that shows up with these problems seems like not a very scalable 
approach. These devices obviously work in Windows, can't we just emulate 
its behavior here?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-01-30 23:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.PeThxrKzzfWoGYao97lEVEZgJlc@ifi.uio.no>
     [not found] ` <fa.SlST1aKbNgZSghdvI9esD81kVnI@ifi.uio.no>
2007-01-30 23:12   ` Robert Hancock [this message]
2007-01-31  1:03     ` [linux-usb-devel] 2.6.20-rc6 SCSI error: I/O error - trouble with mass storage devices ?! Greg KH
2007-01-31  1:06       ` Robert Hancock
2007-01-31 15:20     ` Alan Stern
     [not found] <1169909796.2462.56.camel@localhost>
2007-01-30 18:08 ` Alan Stern
2007-01-31  9:12   ` Soeren Sonnenburg
2007-02-01 21:37   ` Andrew Morton

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=45BFD0F6.9040201@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --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