From: Randy Dunlap <rdunlap@infradead.org>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] vfs: fs_context: Modify mismatched function name
Date: Wed, 19 Oct 2022 20:53:03 -0700 [thread overview]
Message-ID: <c270337a-7be2-e53d-d4e8-81a934907205@infradead.org> (raw)
In-Reply-To: <20221020034036.56523-1-jiapeng.chong@linux.alibaba.com>
Hi--
On 10/19/22 20:40, Jiapeng Chong wrote:
> No functional modification involved.
>
> fs/fs_context.c:347: warning: expecting prototype for vfs_dup_fc_config(). Prototype was for vfs_dup_fs_context() instead.
>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2456
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> fs/fs_context.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/fs_context.c b/fs/fs_context.c
> index df04e5fc6d66..be45701cd998 100644
> --- a/fs/fs_context.c
> +++ b/fs/fs_context.c
> @@ -340,7 +340,7 @@ void fc_drop_locked(struct fs_context *fc)
> static void legacy_fs_context_free(struct fs_context *fc);
>
> /**
> - * vfs_dup_fc_config: Duplicate a filesystem context.
> + * vfs_dup_fs_context: Duplicate a filesystem context.
That is still not the correct kernel-doc format (or syntax).
The ':' should be a '-' instead.
Also, I see scripts/kernel-doc reporting 16 kernel-doc format
problems in this file. How about fixing more than just one of them, please.
fs_context.c:95: warning: No description found for return value of 'vfs_parse_fs
_param_source'
fs_context.c:128: warning: No description found for return value of 'vfs_parse_f
s_param'
fs_context.c:168: warning: Function parameter or member 'fc' not described in 'v
fs_parse_fs_string'
fs_context.c:168: warning: Function parameter or member 'key' not described in '
vfs_parse_fs_string'
fs_context.c:168: warning: Function parameter or member 'value' not described in
'vfs_parse_fs_string'
fs_context.c:168: warning: Function parameter or member 'v_size' not described i
n 'vfs_parse_fs_string'
fs_context.c:168: warning: No description found for return value of 'vfs_parse_f
s_string'
fs_context.c:202: warning: Function parameter or member 'fc' not described in 'g
eneric_parse_monolithic'
fs_context.c:202: warning: Excess function parameter 'ctx' description in 'gener
ic_parse_monolithic'
fs_context.c:202: warning: No description found for return value of 'generic_par
se_monolithic'
fs_context.c:252: warning: No description found for return value of 'alloc_fs_co
ntext'
fs_context.c:340: warning: No description found for return value of 'vfs_dup_fs_
context'
fs_context.c:386: warning: Function parameter or member 'log' not described in '
logfc'
fs_context.c:386: warning: Function parameter or member 'prefix' not described i
n 'logfc'
fs_context.c:386: warning: Function parameter or member 'level' not described in
'logfc'
fs_context.c:386: warning: Excess function parameter 'fc' description in 'logfc'
16 warnings
> * @src_fc: The context to copy.
> */
> struct fs_context *vfs_dup_fs_context(struct fs_context *src_fc)
--
~Randy
prev parent reply other threads:[~2022-10-20 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 3:40 Jiapeng Chong
2022-10-20 3:53 ` 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=c270337a-7be2-e53d-d4e8-81a934907205@infradead.org \
--to=rdunlap@infradead.org \
--cc=abaci@linux.alibaba.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®