From: Rusty Russell <rusty@rustcorp.com.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] add kobject to struct module
Date: Thu, 11 Sep 2003 12:04:35 +1000 [thread overview]
Message-ID: <20030911024252.B26352C04D@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 11 Sep 2003 00:32:47 +0100." <20030911003247.V30046@flint.arm.linux.org.uk>
In message <20030911003247.V30046@flint.arm.linux.org.uk> you write:
> On Tue, Sep 09, 2003 at 03:24:21PM -0700, Greg KH wrote:
> > A while ago we had talked about adding a kobject to struct module. By
> > doing this we add support for module paramaters and other module info to
> > be exported in sysfs. So here's a patch that does this that is against
> > 2.6.0-test4 (it applies with some fuzz, sorry.)
>
> Please excuse my short-sightedness, but I think the following points
> haven't been thought deeply enough:
Well, obviously not publically enough, at least 8(.
To clarify: this is for new-style module params, which explicitly
control their own visibility with the perm arg.
One more reason for module authors to switch 8)
Hope that helps,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2003-09-11 2:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 22:24 [RFC] add kobject to struct module Greg KH
2003-09-10 0:13 ` Greg KH
2003-09-10 3:31 ` Rusty Russell
2003-09-10 4:11 ` Greg KH
2003-09-10 8:07 ` Rusty Russell
2003-09-10 15:26 ` Patrick Mochel
2003-09-11 1:13 ` Rusty Russell
2003-09-11 6:26 ` Greg KH
2003-09-11 8:18 ` Rusty Russell
2003-09-11 17:15 ` Greg KH
2004-02-24 23:29 ` Greg KH
2004-03-05 14:34 ` Rusty Russell
2004-05-07 21:28 ` Greg KH
2003-09-10 23:06 ` Greg KH
2003-09-11 2:33 ` Rusty Russell
2003-09-10 23:32 ` Russell King
2003-09-10 23:45 ` Greg KH
2003-09-11 0:04 ` Mike Fedyk
2003-09-11 0:21 ` Greg KH
2003-09-11 2:10 ` Rusty Russell
2003-09-11 2:04 ` Rusty Russell [this message]
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=20030911024252.B26352C04D@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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.