From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <greg@kroah.com>
Cc: kay.sievers@vrfy.org, linux-kernel@vger.kernel.org
Subject: Re: modprobe bug for aliases with regular expressions
Date: Fri, 14 Apr 2006 14:59:30 +1000 [thread overview]
Message-ID: <1144990770.31267.29.camel@localhost.localdomain> (raw)
In-Reply-To: <20060413233518.GA7597@kroah.com>
On Thu, 2006-04-13 at 16:35 -0700, Greg KH wrote:
> Recently it's been pointed out to me that the modprobe functionality
> with aliases doesn't quite work properly for some USB modules.
Sorry, my bad. I got a patch for this a while ago from Sam Morris.
Originally noone was using ranges in [].
This is fixed in 3.3-pre1. I should release 3.3 proper sometime this
weekend.
Thanks for the poke!
Rusty.
--
ccontrol: http://ozlabs.org/~rusty/ccontrol
next prev parent reply other threads:[~2006-04-14 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 23:35 modprobe bug for aliases with regular expressions Greg KH
2006-04-14 4:59 ` Rusty Russell [this message]
2006-04-14 16:19 ` Greg KH
2006-04-14 5:17 ` Thayumanavar Sachithanantham
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=1144990770.31267.29.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--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