From: Randy Dunlap <rdunlap@infradead.org>
To: Fabien Dessenne <fabien.dessenne@st.com>,
Jessica Yu <jeyu@kernel.org>,
Alexey Gladkov <gladkov.alexey@gmail.com>,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] moduleparam: fix kerneldoc
Date: Fri, 29 Nov 2019 13:40:37 -0800 [thread overview]
Message-ID: <4b6a1030-d84d-b2d6-13ac-e7fa102d039d@infradead.org> (raw)
In-Reply-To: <1575041952-17157-1-git-send-email-fabien.dessenne@st.com>
On 11/29/19 7:39 AM, Fabien Dessenne wrote:
> Document missing @args in xxx_param_cb().
>
> Signed-off-by: Fabien Dessenne <fabien.dessenne@st.com>
> ---
> Changes since v1: do not replace 'lvalue' with 'value'
> ---
> include/linux/moduleparam.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
> index e5c3e23..5215198 100644
> --- a/include/linux/moduleparam.h
> +++ b/include/linux/moduleparam.h
> @@ -160,6 +160,7 @@ struct kparam_array
> * module_param_cb - general callback for a module/cmdline parameter
> * @name: a valid C identifier which is the parameter name.
> * @ops: the set & get operations for this parameter.
> + * @args: args for @ops
should be @arg:
> * @perm: visibility in sysfs.
> *
> * The ops can have NULL set or get functions.
> @@ -176,6 +177,7 @@ struct kparam_array
> * to be evaluated before certain initcall level
> * @name: a valid C identifier which is the parameter name.
> * @ops: the set & get operations for this parameter.
> + * @args: args for @ops
should be @arg:
> * @perm: visibility in sysfs.
> *
> * The ops can have NULL set or get functions.
>
and @level needs to be documented here also.
I tested this patch with
$ ./scripts/kernel-doc -none -function module_param_cb include/linux/moduleparam.h
scripts/kernel-doc does not like this line:
* <level>_param_cb - general callback for a module/cmdline parameter
It needs to match the macro name __level_param_cb.
--
~Randy
prev parent reply other threads:[~2019-11-29 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 15:39 Fabien Dessenne
2019-11-29 21:40 ` Randy Dunlap [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=4b6a1030-d84d-b2d6-13ac-e7fa102d039d@infradead.org \
--to=rdunlap@infradead.org \
--cc=fabien.dessenne@st.com \
--cc=gladkov.alexey@gmail.com \
--cc=glebfm@altlinux.org \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenzhong.duan@oracle.com \
/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
all inboxes | Powered by JetHome®