From: Greg KH <greg@kroah.com>
To: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [RFC] add kobject to struct module
Date: Wed, 10 Sep 2003 17:21:35 -0700 [thread overview]
Message-ID: <20030911002135.GB6996@kroah.com> (raw)
In-Reply-To: <20030911000429.GF1461@matchmail.com>
On Wed, Sep 10, 2003 at 05:04:29PM -0700, Mike Fedyk wrote:
> On Wed, Sep 10, 2003 at 04:45:38PM -0700, Greg KH wrote:
> > To quote from include/linux/moduleparam.h:
> > /* This is the fundamental function for registering boot/module
> > parameters. perm sets the visibility in driverfs: 000 means it's
> > not there, read bits mean it's readable, write bits mean it's
> > writable. */
>
> Any chance to make it always visible and read-only by default with the
> option of making it writable?
I don't know. Doesn't matter to me.
> Exposing the module options would be very helpful.
>
> Also showing its read/write in the sysfs directory listing would be great.
> (if it doesn't already do that).
Look at the permission bits :)
> Any chance the parameter defaults (if they're not hard coded...) could be
> exposed even if they're not given to the module on the command line? (wish
> list...)
That's probably just a modinfo hack.
thanks,
greg k-h
next prev parent reply other threads:[~2003-09-11 0:21 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 [this message]
2003-09-11 2:10 ` Rusty Russell
2003-09-11 2:04 ` Rusty Russell
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=20030911002135.GB6996@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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