Skip to content

Commit

Permalink
Kbuild: enable -Wmaybe-uninitialized warnings by default
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
arndb authored and torvalds committed Nov 11, 2016
1 parent 75ed268 commit 4324cb2
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions scripts/Makefile.extrawarn
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down

0 comments on commit 4324cb2

Please sign in to comment.