From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [PATCH] usb fix
Date: Fri, 31 Aug 2001 15:18:39 -0700 [thread overview]
Message-ID: <20010831151839.C17480@one-eyed-alien.net> (raw)
In-Reply-To: <200108312203.WAA15637@vlet.cwi.nl> <E15cwcv-000477-00@the-village.bc.nu>
In-Reply-To: <E15cwcv-000477-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Aug 31, 2001 at 11:19:01PM +0100
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
That doesn't sound right, Alan...
The constant in question is an upper-limit to the range of device versions
what get accepted. Narrowing the range can only break things -- making it
wider may not (necessarily) fix anything, but it does increase the scope of
the entry.
I'm guessing that someone meant to change it from something smaller than
either Andries' or the current value to where it is now, but the larger
value (i.e. Andries') is the proper one.
Matt
On Fri, Aug 31, 2001 at 11:19:01PM +0100, Alan Cox wrote:
> > but not with 2.4.9, I noticed that my name was added and some
> > constant changed. Changing it back revived my CF reader.
>
> Yes you added the entry, someone changed the constant as it didnt work
> for them, now you change it back.
>
> I suspect both constants should be in 8)
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
We can customize our colonels.
-- Tux
User Friendly, 12/1/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-08-31 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 22:03 Andries.Brouwer
2001-08-31 22:16 ` Matthew Dharm
2001-08-31 22:50 ` Alan Cox
2001-08-31 22:19 ` Alan Cox
2001-08-31 22:18 ` Matthew Dharm [this message]
2001-08-31 22:59 ` Alan Cox
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=20010831151839.C17480@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®