From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what means "module_param(channel_mask, channel_mask, 0644)"?
Date: Sat, 11 Jul 2009 07:07:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0907110704540.4491@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.0907110658370.4257@localhost>
On Sat, 11 Jul 2009, Robert P. J. Day wrote:
> researching my next newbie column about module parameters and i
> ran across the following:
>
> drivers/input/misc/ati_remote2.c:module_param(channel_mask, channel_mask, 0644);
> drivers/input/misc/ati_remote2.c:module_param(mode_mask, mode_mask, 0644);
>
> i have no idea what it means to have the second (type) field of
> module_param() simply repeat the name of the parameter. is this
> some strange magic? those two names don't *appear* to be typedef'ed
> anywhere i can see.
i should have added that the reason i ran across this was that i was
curious if anyone was using User Defined Parameter Types as explained
here:
http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:module_parameters
so i did a quick grep for any invocations of module_param() whose type
wasn't one of the standard int, boot, short, ... etc ... and those two
hits above showed up, which confused me.
so ... *is* anyone taking advantage of user-defined module parameter
types? not as i can tell, but maybe i just missed it.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
next prev parent reply other threads:[~2009-07-11 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 11:01 what means "module_param(channel_mask, channel_mask, 0644)"? Robert P. J. Day
2009-07-11 11:07 ` Robert P. J. Day [this message]
2009-07-11 12:41 ` Paul Bolle
2009-07-11 12:40 ` Robert P. J. Day
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=alpine.LFD.2.00.0907110704540.4491@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@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.