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: Wed, 22 Jun 2011 11:30:12 +0930 [thread overview]
Message-ID: <87r56m8w2b.fsf@rustcorp.com.au> (raw)
In-Reply-To: <BANLkTinL4r3RfNuA5x6=UK4DCSSJNeZw7w@mail.gmail.com>
On Wed, 22 Jun 2011 00:47:55 +0200, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Tue, Jun 21, 2011 at 03:53, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > Sorry, that's another vague answer :(
> >
> > udev already knows about module load
>
> Not for built-ins.
OK, I re-read your commit message, and down the bottom it does say what
it *does*:
> This adds the currently missing /sys/module/<name>/uevent files
> to all module entries.
I apologize for skimming, but this should be the *title* of the patch!
Then I saw your patch hit params.c and thought you were adding a uevent
file to /sys/module/<name>/parameters/. I was even more confused when
you replied:
> Hook system management into module-load events, which might include
> changing module parameters in /sys/module/*/parameters/*...
Because loading a module might *create* module parameters, but it won't
*change* them. If we want to have events for change, we need much
more...
Now we've got that sorted, is there a reason why you changed all the
signatures rather than just using mod->mkobj in store_uevent()?
Thanks,
Rusty.
next prev parent reply other threads:[~2011-06-22 2:43 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 [this message]
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=87r56m8w2b.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