From: Randy Dunlap <rdunlap@infradead.org>
To: Muhammad Muzammil <m.muzzammilashraf@gmail.com>,
corbet@lwn.net, gustavoars@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] scripts: kernel-doc: Bug fixed for erroneous warning
Date: Tue, 19 Dec 2023 22:29:06 -0800 [thread overview]
Message-ID: <4155c90e-cdb1-4645-8bcc-fed4ea01ac83@infradead.org> (raw)
In-Reply-To: <20231220062446.14511-1-muzammil@dreambigsemi.com>
Hi,
On 12/19/23 22:24, Muhammad Muzammil wrote:
> From: Muzammil Ashraf <m.muzzammilashraf@gmail.com>
>
> kernel-doc: fixed erroneous warning generated by '__counted_by'
>
> Signed-off-by: Muzammil Ashraf <m.muzzammilashraf@gmail.com>
> ---
> scripts/kernel-doc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/kernel-doc b/scripts/kernel-doc
> index 1484127db104..ea9688df0e93 100755
> --- a/scripts/kernel-doc
> +++ b/scripts/kernel-doc
> @@ -1661,6 +1661,7 @@ sub check_sections($$$$$) {
> }
> elsif (($decl_type eq "struct") or
> ($decl_type eq "union")) {
> + next if (index("@_", "__counted_by") != -1);
> emit_warning("${file}:$.",
> "Excess $decl_type member " .
> "'$sects[$sx]' " .
One of both of these patches should be enough. Can you test these
instead of your patch, please?
https://lore.kernel.org/linux-doc/20231215001347.work.151-kees@kernel.org/
https://lore.kernel.org/linux-doc/87le9rjb4y.fsf@meer.lwn.net/
Thanks.
--
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html
next prev parent reply other threads:[~2023-12-20 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 6:24 [PATCH] scripts: kernel-doc: Bug fixed for erroneous warning Muhammad Muzammil
2023-12-20 6:29 ` Randy Dunlap [this message]
2023-12-20 6:35 ` Muhammad Muzammil
2023-12-20 6:49 ` Randy Dunlap
2023-12-20 6:30 ` Greg KH
2023-12-20 15:30 ` Jonathan Corbet
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=4155c90e-cdb1-4645-8bcc-fed4ea01ac83@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=gustavoars@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.muzzammilashraf@gmail.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