From: Nathaniel McCallum <nathaniel@natemccallum.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Devices that ignore USB spec generate invalid modaliases
Date: Wed, 11 Nov 2009 03:39:41 -0500 [thread overview]
Message-ID: <4AFA784D.1060001@natemccallum.com> (raw)
In-Reply-To: <4AFA73C7.4070002@natemccallum.com>
On 11/11/2009 03:20 AM, Nathaniel McCallum wrote:
> Drivers for devices which have bcdDevice conforming to BCD will have no
> change in modalias output.
One small clarification. Existing drivers which specify a non-zero lower
bound and an upper bound past the next character will have their upper
bound changed from 0x9 to 0xf (i.e.: d123[4-9] -> d123[4-9a-f]). I
believe this is the only case where an existing (working) modalias will
change.
Nathaniel McCallum
next prev parent reply other threads:[~2009-11-11 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 8:20 [PATCH] Devices that ignore USB spec generate invalid modaliases Nathaniel McCallum
2009-11-11 8:39 ` Nathaniel McCallum [this message]
2009-11-11 18:54 ` [PATCH][RFC] " Nathaniel McCallum
2009-11-12 23:42 ` [PATCH] " Greg KH
2009-11-13 1:09 ` Nathaniel McCallum
2009-11-13 14:51 ` Nathaniel McCallum
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=4AFA784D.1060001@natemccallum.com \
--to=nathaniel@natemccallum.com \
--cc=linux-kernel@vger.kernel.org \
/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