From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Stelian Pop <stelian@popies.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.de>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] drivers/net/pcmcia: use module_param() instead of MODULE_PARM()
Date: Wed, 10 Nov 2004 08:35:05 -0800 [thread overview]
Message-ID: <41924339.1070809@osdl.org> (raw)
In-Reply-To: <20041110160058.GB8542@sd291.sivit.org>
Hi Stelian,
Several of these changes expose module parameters to sysfs
(i.e., have permissions of non-zero value) without need for that IMO.
This came up yesterday on the kernel-janitors mailing list.
When asked about it, Greg KH replied:
> Can someone please clarify the "official guidelines" for
> module parameter permissions in sysfs?
"When it makes sense to have it exposed to userspace"
Yeah, it's vague, sorry, but it all depends.
For things that can be changed on the fly, expose it.
For things that don't really matter, and no one will ever look them up,
don't. I think the irq stuff is in the "don't" category, as almost no
one messes with them anymore.
<end quote>
OTOH, debug flags are often read/write and visible, so using
0644 for them is the right thing to do.
Stelian Pop wrote:
ChangeSet@1.2090, 2004-11-10 16:43:13+01:00, stelian@popies.net
drivers/net/pcmcia: use module_param() instead of MODULE_PARM()
Signed-off-by: Stelian Pop <stelian@popies.net>
===================================================================
3c574_cs.c | 21 +++++++++++++--------
3c589_cs.c | 18 ++++++++++--------
axnet_cs.c | 11 ++++++-----
com20020_cs.c | 34 +++++++++++++++++-----------------
fmvj18x_cs.c | 15 ++++++++-------
ibmtr_cs.c | 23 ++++++++++++-----------
nmclan_cs.c | 14 ++++++++------
pcnet_cs.c | 46 +++++++++++++++++++++++++++++++++-------------
smc91c92_cs.c | 18 ++++++++++--------
xirc2ps_cs.c | 25 +++++++++++++++++--------
10 files changed, 134 insertions(+), 91 deletions(-)
===================================================================
--
~Randy
next prev parent reply other threads:[~2004-11-10 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 11:27 [PATCH RESEND] pcmcia network drivers cleanup Stelian Pop
2004-11-05 2:25 ` Jeff Garzik
2004-11-05 8:32 ` Stelian Pop
2004-11-10 15:59 ` Stelian Pop
2004-11-10 16:00 ` [PATCH] drivers/net/pcmcia: use module_param() instead of MODULE_PARM() Stelian Pop
2004-11-10 16:35 ` Randy.Dunlap [this message]
2004-11-10 19:52 ` Stelian Pop
2004-11-10 19:47 ` Randy.Dunlap
2004-11-10 21:21 ` Stelian Pop
2004-11-13 22:44 ` Dominik Brodowski
2004-11-10 16:01 ` [PATCH] drivers/net/pcmcia: rework debugging Stelian Pop
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=41924339.1070809@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.de \
--cc=stelian@popies.net \
/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