Date: Wed, 10 Sep 2003 17:04:29 -0700
From: Mike Fedyk <mfedyk@matchmail.com>
To: Greg KH <greg@kroah.com>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [RFC] add kobject to struct module
Message-ID: <20030911000429.GF1461@matchmail.com>
Mail-Followup-To: Greg KH <greg@kroah.com>, rusty@rustcorp.com.au,
	linux-kernel@vger.kernel.org
References: <20030909222421.GA7703@kroah.com> <20030911003247.V30046@flint.arm.linux.org.uk> <20030910234538.GB6719@kroah.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030910234538.GB6719@kroah.com>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 991
Lines: 23

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?

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).

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...)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/