From: Greg KH <gregkh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] drivers/usb/core/usb.c: add MODNAME env var to hotplug
Date: Thu, 24 Mar 2005 22:34:59 +0000 [thread overview]
Message-ID: <20050324223459.GA27496@kroah.com> (raw)
In-Reply-To: <20050304100158.GB2219@katya>
On Fri, Mar 04, 2005 at 01:01:58PM +0300, Roman Kagan wrote:
> Hi,
>
> The patch below adds MODNAME environment variable to usb hotplug
> callout, allowing for its straightforward use with modprobe.
Sorry for the delay, but I've now added this. I changed the variable
name to MODALIAS to make it match up with what it really is referring
to.
> The patch expects a matching change in scripts/mod/file2alias.c I sent
> to linux-hotplug-devel list a few days ago (i.e. puts
> bcdDevice in MODNAME as dXXXX, rather that dlXXXXdhXXXX).
I changed this back, as this change doesn't seem to have gone anywhere.
thanks,
greg k-h
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-03-24 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 10:01 [PATCH] drivers/usb/core/usb.c: add MODNAME env var to hotplug Roman Kagan
2005-03-24 22:34 ` Greg KH [this message]
2005-03-25 7:43 ` Roman Kagan
2005-03-25 17:40 ` Greg KH
2005-03-26 19:54 ` [linux-usb-devel] Re: [PATCH] drivers/usb/core/usb.c: add MODNAME Michael Tokarev
2005-03-27 20:36 ` [linux-usb-devel] Re: [PATCH] drivers/usb/core/usb.c: add MODNAME env var to hotplug Roman Kagan
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=20050324223459.GA27496@kroah.com \
--to=gregkh@suse.de \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.