public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Muhammad Muzammil <m.muzzammilashraf@gmail.com>,
	rdunlap@infradead.org, gustavoars@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org,
	Muzammil Ashraf <m.muzzammilashraf@gmail.com>
Subject: Re: [PATCH] scripts: kernel-doc: Bug fixed for erroneous warning
Date: Wed, 20 Dec 2023 08:30:03 -0700	[thread overview]
Message-ID: <87edfggadg.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231220062446.14511-1-muzammil@dreambigsemi.com>

Muhammad Muzammil <m.muzzammilashraf@gmail.com> writes:

> 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]' " .

Could you give an example of the warnings that this patch addresses?
I've not seen any caused by __counted_by since f600c77aeaff was applied
to docs-next.  What did it miss?

Thanks,

jon

      parent reply	other threads:[~2023-12-20 15:30 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
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 [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=87edfggadg.fsf@meer.lwn.net \
    --to=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 \
    --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