From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Andries.Brouwer@cwi.nl, greg@kroah.com,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
USB Storage List <usb-storage@lists.one-eyed-alien.net>
Subject: Re: [patch] datafab fix and unusual devices
Date: Tue, 30 Mar 2004 01:38:13 +0200 [thread overview]
Message-ID: <20040329233812.GA17179@apps.cwi.nl> (raw)
In-Reply-To: <20040329231508.GH28472@one-eyed-alien.net>
On Mon, Mar 29, 2004 at 03:15:08PM -0800, Matthew Dharm wrote:
> On Tue, Mar 30, 2004 at 12:44:09AM +0200, Andries.Brouwer@cwi.nl wrote:
> > datafab.c has an often-seen bug: the SCSI READ_CAPACITY command
> > does not need the number of sectors but the last sector.
>
> The first part of the patch (which fixes this bug) certainly looks good to
> me for 2.6 -- we need to check that 2.4 doesn't also have the problem.
>
> The second part of your patch I don't like (it seems to violate the
> 'principal of least suprise' to me).... but I'm also ready and willing to
> consider a beter alternative. What do you suggest?
Well, the entire patch should be applied. Nothing wrong with it.
That will enable people to use (0x0c0b,0xa109) to read CF,
or to read SM, but not both. (Without the patch the device
does not work at all.)
The situation is precisely the same as that for (0x07c4,0xa109).
To do something better we need infrastructure that does not exist today,
at least not in the vanilla kernel. That is why I call for discussion.
The points are ordinary use and error recovery.
For ordinary use the main point seems to be the us->extra
pointer to private data. Since each driver needs private data,
a single pointer does not suffice.
Andries
next prev parent reply other threads:[~2004-03-29 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 22:44 [patch] datafab fix and unusual devices Andries.Brouwer
2004-03-29 23:15 ` Matthew Dharm
2004-03-29 23:38 ` Andries Brouwer [this message]
2004-03-30 21:56 ` Greg KH
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=20040329233812.GA17179@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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