From: Jonathan Corbet <corbet@lwn.net>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH v2 1/2] kernel-doc: don't let V=1 change outcome
Date: Fri, 09 Jun 2023 02:26:48 -0600 [thread overview]
Message-ID: <87edmloxbr.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230606105706.60807b85ff79.I21ab3b54eeebd638676bead3b2f87417944e44f3@changeid>
Johannes Berg <johannes@sipsolutions.net> writes:
> From: Johannes Berg <johannes.berg@intel.com>
>
> The kernel-doc script currently reports a number of issues
> only in "verbose" mode, but that's initialized from V=1
> (via KBUILD_VERBOSE), so if you use KDOC_WERROR=1 then
> adding V=1 might actually break the build. This is rather
> unexpected.
>
> Change kernel-doc to not change its behaviour wrt. errors
> (or warnings) when verbose mode is enabled, but rather add
> separate warning flags (and -Wall) for it. Allow enabling
> those flags via environment/make variables in the kernel's
> build system for easier user use, but to not have to parse
> them in the script itself.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> v2: - parse environment variables in build system rather than
> the script itself, as suggested by Masahiro Yamada
> - fix indentation
So this change seems fine to me; Masahiro, if you want to take these,
feel free to add:
Acked-by: Jonathan Corbet <corbet@lwn.net>
Thanks,
jon
prev parent reply other threads:[~2023-06-09 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:57 [PATCH v2 1/2] kernel-doc: don't let V=1 change outcome Johannes Berg
2023-06-06 8:57 ` [PATCH v2 2/2] kbuild: enable kernel-doc -Wall for W=2 Johannes Berg
2023-06-06 11:15 ` [PATCH v2 1/2] kernel-doc: don't let V=1 change outcome Masahiro Yamada
2023-06-06 21:07 ` Johannes Berg
2023-06-07 23:51 ` Masahiro Yamada
2023-06-09 8:42 ` Johannes Berg
2023-06-09 8:26 ` 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=87edmloxbr.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.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).