From: Jonathan Corbet <corbet@lwn.net>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/kernel-doc: Do not track section counter across processed files
Date: Mon, 14 Oct 2024 12:21:59 -0600 [thread overview]
Message-ID: <87iktusfy0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241008082905.4005524-1-wenst@chromium.org>
Chen-Yu Tsai <wenst@chromium.org> writes:
> The section counter tracks how many sections of kernel-doc were added.
> The only real use of the counter value is to check if anything was
> actually supposed to be output and give a warning is nothing is
> available.
>
> The current logic of remembering the initial value and then resetting
> the value then when processing each file means that if a file has the
> same number of sections as the previously processed one, a warning is
> incorrectly given.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
> ---
> Found this while improving and checking the kernel docs for the
> regulator core.
>
> scripts/kernel-doc | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/scripts/kernel-doc b/scripts/kernel-doc
> index 2791f8195203..c608820f0bf5 100755
> --- a/scripts/kernel-doc
> +++ b/scripts/kernel-doc
> @@ -2322,7 +2322,6 @@ sub process_inline($$) {
>
> sub process_file($) {
> my $file;
> - my $initial_section_counter = $section_counter;
> my ($orig_file) = @_;
>
> $file = map_filename($orig_file);
> @@ -2360,8 +2359,7 @@ sub process_file($) {
> }
>
> # Make sure we got something interesting.
> - if ($initial_section_counter == $section_counter && $
> - output_mode ne "none") {
> + if (!$section_counter && $output_mode ne "none") {
> if ($output_selection == OUTPUT_INCLUDE) {
> emit_warning("${file}:1", "'$_' not found\n")
> for keys %function_table;
So I am curious, have you actually seen a spurious warning from this? A
normal build does not emit any here.
The current logic is indeed screwy, I'll apply this fix. But
$section_counter kind of seems like a holdover from the docbook days and
maybe isn't needed at all anymore?
Thanks,
jon
next prev parent reply other threads:[~2024-10-14 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 8:29 [PATCH] scripts/kernel-doc: Do not track section counter across processed files Chen-Yu Tsai
2024-10-14 18:21 ` Jonathan Corbet [this message]
2024-10-16 4:15 ` Chen-Yu Tsai
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=87iktusfy0.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wenst@chromium.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