1
0
Fork 0

Kbuild: enable -Wmaybe-uninitialized warnings by default

Previously the warnings were added back at the W=1 level and above, this
now turns them on again by default, assuming that we have addressed all
warnings and again have a clean build for v4.10.

I found a number of new warnings in linux-next already and submitted
bugfixes for those.  Hopefully they are caught by the 0day builder in
the future as soon as this patch is merged.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
hifive-unleashed-5.1
Arnd Bergmann 2016-11-10 17:44:54 +01:00 committed by Linus Torvalds
parent 75ed26878b
commit 4324cb23f4
1 changed files with 0 additions and 2 deletions

View File

@ -60,8 +60,6 @@ endif
KBUILD_CFLAGS += $(warning)
else
KBUILD_CFLAGS += $(call cc-disable-warning, maybe-uninitialized)
ifeq ($(cc-name),clang)
KBUILD_CFLAGS += $(call cc-disable-warning, initializer-overrides)
KBUILD_CFLAGS += $(call cc-disable-warning, unused-value)