From: Jonathan Corbet <corbet@lwn.net>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-doc@vger.kernel.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Carlos Bilbao <carlos.bilbao@amd.com>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH] doc: Always check kernel-doc
Date: Fri, 18 Aug 2023 10:49:37 -0600 [thread overview]
Message-ID: <87cyzkmh26.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230817144142.903553-1-willy@infradead.org>
"Matthew Wilcox (Oracle)" <willy@infradead.org> writes:
> kernel-doc checks were initially enabled only for builds which had extra
> warnings enabled. We have now eliminated enough kernel-doc warnings that
> we can enable kernel-doc checking by default. This comes at a slight
> cost; for an allmodconfig build, make -j8 fs/ timings on my laptop
> increase by less than 5%:
>
> before real 4m7.456s 4m4.416s 4m6.663s
> after real 4m18.960s 4m21.566s 4m23.234s
> before user 29m35.370s 29m11.036s 29m30.092s
> after user 30m55.602s 31m10.918s 31m20.311s
> before sys 2m8.230s 2m6.392s 2m9.727s
> after sys 2m19.896 2m23.422s 2m25.762s
>
> This feels like a reasonable price to pay to force people to keep
> documentation up to date.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Reviewed-by: Carlos Bilbao <carlos.bilbao@amd.com>
> ---
> scripts/Makefile.build | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/scripts/Makefile.build b/scripts/Makefile.build
> index 82e3fb19fdaf..52f57c0c5227 100644
> --- a/scripts/Makefile.build
> +++ b/scripts/Makefile.build
> @@ -100,11 +100,9 @@ else ifeq ($(KBUILD_CHECKSRC),2)
> cmd_force_checksrc = $(CHECK) $(CHECKFLAGS) $(c_flags) $<
> endif
>
> -ifneq ($(KBUILD_EXTRA_WARN),)
> - cmd_checkdoc = $(srctree)/scripts/kernel-doc -none $(KDOCFLAGS) \
> +cmd_checkdoc = $(srctree)/scripts/kernel-doc -none $(KDOCFLAGS) \
> $(if $(findstring 2, $(KBUILD_EXTRA_WARN)), -Wall) \
> $<
> -endif
>
So I'm not opposed to this and can carry it in docs-next (after the
merge window, though, for something like this). But, it seems to me, we
should copy Masahiro (added) on a build patch of this type.
Thanks,
jon
next prev parent reply other threads:[~2023-08-18 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 14:41 [PATCH] doc: Always check kernel-doc Matthew Wilcox (Oracle)
2023-08-18 16:49 ` Jonathan Corbet [this message]
2023-08-18 17:14 ` Matthew Wilcox
2023-08-18 17:19 ` Jonathan Corbet
2023-08-19 22:48 ` Masahiro Yamada
2023-10-07 3:57 ` Matthew Wilcox
2023-10-09 9:47 ` Jani Nikula
2023-10-03 18:38 ` Jonathan Corbet
2023-10-04 15:15 ` Jani Nikula
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=87cyzkmh26.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=carlos.bilbao@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=willy@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).