From: Rusty Russell <rusty@rustcorp.com.au>
To: Raphael Hertzog <hertzog@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Some kernel module options not showing up in modinfo
Date: Sun, 01 Dec 2013 08:46:59 +1030 [thread overview]
Message-ID: <87k3fpfsbo.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20131122073454.GE17630@x230-buxy.home.ouaza.com>
Raphael Hertzog <hertzog@debian.org> writes:
> Hi,
>
> On Fri, 22 Nov 2013, Rusty Russell wrote:
>> Raphael Hertzog <hertzog@debian.org> writes:
>> > Hello,
>> >
>> > I noticed that some options are not visible in the modinfo output. For
>> > instance "modinfo lockd" reports this on my Debian sid system:
> [...]
>> > Multiple other options are defined by way of module_param_call(...) like
>> > nlm_grace_period, nlm_timeout, nlm_updport, nlm_tcpport.
>>
>> Yes, the module_param() macro adds a type description. The
>> module_param_call() does not.
>
> Couldn't they be displayed without any type or with a type "unknown" ?
>
> parm: nlm_grace_period
>
> or
>
> parm: nlm_grace_period:unknown
The type thing is really a hack. Ideally we should force documentation
on everyone who declares a module parameter with a new macro we can
transition to.
Of course, most descriptions would be incoherent, a-la Kbuild help
messages, so we'd need an enforcer...
Rusty.
prev parent reply other threads:[~2013-12-01 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 14:47 Some kernel module options not showing up in modinfo Raphael Hertzog
2013-11-22 2:36 ` Rusty Russell
2013-11-22 7:34 ` Raphael Hertzog
2013-11-30 22:16 ` Rusty Russell [this message]
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=87k3fpfsbo.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=hertzog@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox