From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Richard Weinberger <richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ubifs: fix kernel-doc warnings
Date: Mon, 6 May 2024 10:11:53 +0800 [thread overview]
Message-ID: <c94ba482-0b3a-e8c0-0990-dcb5507148c6@huawei.com> (raw)
In-Reply-To: <20240502-ubifs-kdoc-v1-1-59c35a325141@quicinc.com>
在 2024/5/3 4:16, Jeff Johnson 写道:
> make C=1 reports the following kernel-doc warnings:
>
> fs/ubifs/compress.c:103: warning: Function parameter or struct member 'c' not described in 'ubifs_compress'
> fs/ubifs/compress.c:155: warning: Function parameter or struct member 'c' not described in 'ubifs_decompress'
> fs/ubifs/find.c:353: warning: Excess function parameter 'data' description in 'scan_for_free_cb'
> fs/ubifs/find.c:353: warning: Function parameter or struct member 'arg' not described in 'scan_for_free_cb'
> fs/ubifs/find.c:594: warning: Excess function parameter 'data' description in 'scan_for_idx_cb'
> fs/ubifs/find.c:594: warning: Function parameter or struct member 'arg' not described in 'scan_for_idx_cb'
> fs/ubifs/find.c:786: warning: Excess function parameter 'data' description in 'scan_dirty_idx_cb'
> fs/ubifs/find.c:786: warning: Function parameter or struct member 'arg' not described in 'scan_dirty_idx_cb'
> fs/ubifs/find.c:86: warning: Excess function parameter 'data' description in 'scan_for_dirty_cb'
> fs/ubifs/find.c:86: warning: Function parameter or struct member 'arg' not described in 'scan_for_dirty_cb'
> fs/ubifs/journal.c:369: warning: expecting prototype for wake_up_reservation(). Prototype was for add_or_start_queue() instead
> fs/ubifs/lprops.c:1018: warning: Excess function parameter 'lst' description in 'scan_check_cb'
> fs/ubifs/lprops.c:1018: warning: Function parameter or struct member 'arg' not described in 'scan_check_cb'
> fs/ubifs/lpt.c:1938: warning: Function parameter or struct member 'ptr' not described in 'lpt_scan_node'
> fs/ubifs/replay.c:60: warning: Function parameter or struct member 'hash' not described in 'replay_entry'
>
> Fix them.
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
> Note ubifs still has C=1 warnings from smatch that are not addressed:
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
>
[...]
> diff --git a/fs/ubifs/journal.c b/fs/ubifs/journal.c
> index 74aee92433d7..f997a85bcdce 100644
> --- a/fs/ubifs/journal.c
> +++ b/fs/ubifs/journal.c
> @@ -359,7 +359,7 @@ static void wake_up_reservation(struct ubifs_info *c)
> }
>
> /**
> - * wake_up_reservation - add current task in queue or start queuing.
> + * add_or_start_queue - add current task in queue or start queuing.
> * @c: UBIFS file-system description object
> *
> * This function starts queuing if queuing is not started, otherwise adds
This period of code was modified in previous patch
https://patchwork.ozlabs.org/project/linux-mtd/patch/20240227024204.1080739-1-chengzhihao1@huawei.com/
, I'm okay to drop the old patch and apply this one.
prev parent reply other threads:[~2024-05-06 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 20:16 Jeff Johnson
2024-05-06 2:11 ` Zhihao Cheng [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=c94ba482-0b3a-e8c0-0990-dcb5507148c6@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=quic_jjohnson@quicinc.com \
--cc=richard@nod.at \
/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®