From: "Randy.Dunlap" <rddunlap@osdl.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] convert airo wireless driver to module_param
Date: Tue, 09 Nov 2004 21:38:18 +0000 [thread overview]
Message-ID: <419138CA.4030802@osdl.org> (raw)
In-Reply-To: <20041109212957.GA9496@dice.seeling33.de>
Stefan Sperling wrote:
> Replaces MODULE_PARM with module_param calls in airo wireless driver.
>
> --- drivers/net/wireless/airo.c.orig 2004-11-09 20:40:21.867942880 +0100
> +++ drivers/net/wireless/airo.c 2004-11-08 23:09:27.000000000 +0100
> @@ -246,36 +246,36 @@ MODULE_DESCRIPTION("Support for Cisco/Ai
> for PCMCIA when used with airo_cs.");
> MODULE_LICENSE("Dual BSD/GPL");
> MODULE_SUPPORTED_DEVICE("Aironet 4500, 4800 and Cisco 340/350");
> -MODULE_PARM(io,"1-4i");
> -MODULE_PARM(irq,"1-4i");
> -MODULE_PARM(basic_rate,"i");
> -MODULE_PARM(rates,"1-8i");
> -MODULE_PARM(ssids,"1-3s");
> -MODULE_PARM(auto_wep,"i");
> +module_param_array(io, int, NULL, 0444);
> +module_param_array(irq, int, NULL, 0444);
> +module_param(basic_rate, int, 0644);
> +module_param_array(rates, int, NULL, 0644);
> +module_param_array(ssids, int, NULL, 0644);
Why make these writable, even by root?
Why make them visible?
Rusty's first set of module_param() conversion patches, which
I mostly followed, use permission (last parameter) of 0
(not visible in sysfs) except for fields that can be modified.
Often this is a "debug" or "verbose" flag or bitmask.
Many of these shouldn't be exposed in sysfs IMO.
> +module_param(auto_wep, int, 0644);
> MODULE_PARM_DESC(auto_wep, "If non-zero, the driver will keep looping through \
> the authentication options until an association is made. The value of \
> auto_wep is number of the wep keys to check. A value of 2 will try using \
> the key at index 0 and index 1.");
> -MODULE_PARM(aux_bap,"i");
> +module_param(aux_bap, int, 0644);
> MODULE_PARM_DESC(aux_bap, "If non-zero, the driver will switch into a mode \
> than seems to work better for older cards with some older buses. Before \
> switching it checks that the switch is needed.");
> -MODULE_PARM(maxencrypt, "i");
> +module_param(maxencrypt, int, 0644);
> MODULE_PARM_DESC(maxencrypt, "The maximum speed that the card can do \
> encryption. Units are in 512kbs. Zero (default) means there is no limit. \
> Older cards used to be limited to 2mbs (4).");
> -MODULE_PARM(adhoc, "i");
> +module_param(adhoc, int, 0644);
> MODULE_PARM_DESC(adhoc, "If non-zero, the card will start in adhoc mode.");
> -MODULE_PARM(probe, "i");
> +module_param(probe, int, 0644);
> MODULE_PARM_DESC(probe, "If zero, the driver won't start the card.");
>
> -MODULE_PARM(proc_uid, "i");
> +module_param(proc_uid, int, 0644);
> MODULE_PARM_DESC(proc_uid, "The uid that the /proc files will belong to.");
> -MODULE_PARM(proc_gid, "i");
> +module_param(proc_gid, int, 0644);
> MODULE_PARM_DESC(proc_gid, "The gid that the /proc files will belong to.");
> -MODULE_PARM(airo_perm, "i");
> +module_param(airo_perm, int, 0644);
> MODULE_PARM_DESC(airo_perm, "The permission bits of /proc/[driver/]aironet.");
> -MODULE_PARM(proc_perm, "i");
> +module_param(proc_perm, int, 0644);
> MODULE_PARM_DESC(proc_perm, "The permission bits of the files in /proc");
--
~Randy
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-11-09 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 21:29 [KJ] [PATCH] convert airo wireless driver to module_param Stefan Sperling
2004-11-09 21:38 ` Randy.Dunlap [this message]
2004-11-09 22:05 ` Stefan Sperling
2004-11-09 22:21 ` Stefan Sperling
2004-11-09 22:28 ` Randy.Dunlap
2004-11-09 22:29 ` Greg KH
2004-11-09 22:29 ` Randy.Dunlap
2004-11-09 22:56 ` Stefan Sperling
2004-11-09 22:58 ` Stefan Sperling
2004-11-09 23:16 ` Stefan Sperling
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=419138CA.4030802@osdl.org \
--to=rddunlap@osdl.org \
--cc=kernel-janitors@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 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.