Re: [RFC v2 01/39] Kconfig: introduce HAS_IOPORT option and select it as necessary
From: Finn Thain <fthain@linux-m68k.org>
Date: 2022-05-08 00:15:55
Also in:
linux-alpha, linux-arch, linux-m68k, linux-mips, linux-pci, linux-riscv, linux-sh, linuxppc-dev, lkml, sparclinux
Subsystem:
the rest · Maintainer:
Linus Torvalds
On Sun, 8 May 2022, I wrote:
That suggests to me that we need a "bool CONFIG_WARINGS_INTO_ERRORS" to control -Werror, which could be disabled for .config files (like make allmodconfig) where it is not helping.
I just noticed that we already have CONFIG_WERROR. So perhaps something like this would help.
diff --git a/init/Kconfig b/init/Kconfig
index ddcbefe535e9..765d83fb148e 100644
--- a/init/Kconfig
+++ b/init/Kconfig@@ -150,6 +150,8 @@ config WERROR However, if you have a new (or very old) compiler with odd and unusual warnings, or you have some architecture with problems, + or if you are using a compiler that doesn't happen to interpret + the C standards in quite the same way as some other compilers, you may need to disable this config option in order to successfully build the kernel.
_______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel