From: Simon Horman <horms@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath: wil6210: fix a bunch of kernel-doc warnings
Date: Fri, 21 Nov 2025 13:04:46 +0000 [thread overview]
Message-ID: <aSBjbqQtQFgRTDS0@horms.kernel.org> (raw)
In-Reply-To: <20251117020213.443126-1-rdunlap@infradead.org>
On Sun, Nov 16, 2025 at 06:02:13PM -0800, Randy Dunlap wrote:
> scripts/kernel-doc.py reports 51 kernel-doc warnings in wil6210.h.
> Fix all kernel-doc warnings reported in wil6210.h.
>
> Several comments are changed from "/**" to "/*" since it appears that
> "/**" was used for many non-kernel-doc comments.
>
> - add kernel-doc for missing function parameters
> - add one function "Returns:"
> - correct kernel-doc struct name to match actual struct name in 2 places
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
...
> @@ -444,8 +444,7 @@ static inline u8 mk_cidxtid(u8 cid, u8 t
> * parse_cidxtid - parse @cidxtid field
> * @cid: store CID value here
> * @tid: store TID value here
> - *
> - * @cidxtid field encoded as bits 0..3 - CID; 4..7 - TID
> + * @cidxtid: field encoded as bits 0..3 - CID; 4..7 - TID
Hi Randy,
I wonder if it would make sense to move the @cidxtid line
so it is above the @cid line. In which case the order of
the documentation of the parameters would match their order
in the subject.
But either way, this patch looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
> */
> static inline void parse_cidxtid(u8 cidxtid, u8 *cid, u8 *tid)
> {
...
next prev parent reply other threads:[~2025-11-21 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 2:02 [PATCH] ath: wil6210: fix a bunch of kernel-doc warnings Randy Dunlap
2025-11-21 13:04 ` Simon Horman [this message]
2025-11-22 5:26 ` Randy Dunlap
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=aSBjbqQtQFgRTDS0@horms.kernel.org \
--to=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).