From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <greg@kroah.com>, Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: module: sysfs - add 'uevent' file to allow coldplug
Date: Mon, 04 Jul 2011 14:26:21 +0930 [thread overview]
Message-ID: <87k4bysky2.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20110701211449.GB19805@kroah.com>
On Fri, 1 Jul 2011 14:14:49 -0700, Greg KH <greg@kroah.com> wrote:
> On Sun, Jun 19, 2011 at 12:00:29AM +0200, Kay Sievers wrote:
> > From: Kay Sievers <kay.sievers@vrfy.org>
> > Subject: module: sysfs - add 'uevent' file to allow built-in coldplug
> >
> > Userspace wants to manage module parameters with udev rules.
> > This currently only works for loaded modules, but not for
> > built-in ones.
> >
> > To allow access to the built-in modules we need to
> > re-trigger all module load events that happened before any
> > userspace was running. We already do the same thing for all
> > devices, subsystems(buses) and drivers.
> >
> > This adds the currently missing /sys/module/<name>/uevent files
> > to all module entries.
> >
> > Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
>
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> Rusty, are you going to take this in your tree?
Yep, done.
Thanks,
Rusty.
next prev parent reply other threads:[~2011-07-04 5:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 22:00 module: sysfs - add 'uevent' file to allow coldplug Kay Sievers
2011-06-19 23:23 ` Rusty Russell
2011-06-20 11:20 ` Kay Sievers
2011-06-21 1:53 ` Rusty Russell
2011-06-21 22:47 ` Kay Sievers
2011-06-22 2:00 ` Rusty Russell
2011-06-22 10:17 ` Kay Sievers
2011-06-23 0:27 ` Rusty Russell
2011-06-23 11:24 ` Kay Sievers
2011-07-01 3:07 ` Kay Sievers
2011-07-04 5:05 ` Rusty Russell
2011-07-04 15:56 ` Kay Sievers
2011-07-06 5:27 ` Rusty Russell
2011-07-01 21:14 ` Greg KH
2011-07-04 4:56 ` Rusty Russell [this message]
2011-07-04 15:28 ` 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=87k4bysky2.fsf@rustcorp.com.au \
--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