public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: module: sysfs - add 'uevent' file to allow coldplug
Date: Tue, 21 Jun 2011 11:23:05 +0930	[thread overview]
Message-ID: <87boxshrwe.fsf@rustcorp.com.au> (raw)
In-Reply-To: <BANLkTink8YTe=-Tr5Ax3epiFoFCfzcex7w@mail.gmail.com>

On Mon, 20 Jun 2011 13:20:00 +0200, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Mon, Jun 20, 2011 at 01:23, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > On Sun, 19 Jun 2011 00:00:29 +0200, Kay Sievers <kay.sievers@vrfy.org> 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.
> >
> > I'm confused.  What does "manage" mean here?
> 
> Hook system management into module-load events, which might include
> changing module parameters in /sys/module/*/parameters/*, or at
> bootup/coldplug run it for built-in modules.
> 
> We do the same to set properties for buses, drivers or devices when they appear.

Sorry, that's another vague answer :(

udev already knows about module load, and the parameters are created at
that point; they are not *changed*.

What, *exactly* will this enable?  Don't use the word "hook" or
"management": both vague terms which assume I know what you're talking
about.  I don't.

Show me exactly what udev will now be able to do that it can't do now,
and how it will be used.  Preferably with examples.  Assume (correctly)
that I have only a vague idea what udev does.

Thanks,
Rusty.

  reply	other threads:[~2011-06-21 22:07 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 [this message]
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
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=87boxshrwe.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