summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2023-06-09 10:46:41 +0200
committerMasahiro Yamada <masahiroy@kernel.org>2023-06-10 09:39:02 +0200
commit56b0f453db74207633019f83758b4c11c66b75d0 (patch)
tree4fcd1efc4a45afdd59aeda5ca3b3fe4afa6ab1cd /security
parentmodpost: fix off by one in is_executable_section() (diff)
downloadlinux-56b0f453db74207633019f83758b4c11c66b75d0.tar.xz
linux-56b0f453db74207633019f83758b4c11c66b75d0.zip
kernel-doc: don't let V=1 change outcome
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> Acked-by: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions