[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1507074806-21577-1-git-send-email-ulfalizer@gmail.com>
Date: Wed, 4 Oct 2017 01:53:26 +0200
From: Ulf Magnusson <ulfalizer@...il.com>
To: linux-kernel@...r.kernel.org
Cc: linux-kbuild@...r.kernel.org, paulmck@...ux.vnet.ibm.com,
nicolas.pitre@...aro.org, akpm@...ux-foundation.org, tj@...nel.org,
tglx@...utronix.de, keescook@...omium.org, daniel@...que.org,
arnd@...db.de, Ulf Magnusson <ulfalizer@...il.com>
Subject: [PATCH] kbuild: Fix optimization level choice default
The choice containing the CC_OPTIMIZE_FOR_PERFORMANCE symbol
accidentally added a "CONFIG_" prefix when trying to make it the
default, selecting an undefined symbol as the default.
The mistake is harmless here: Since the default symbol is not visible,
the choice falls back on using the visible symbol as the default
instead, which is CC_OPTIMIZE_FOR_PERFORMANCE, as intended.
A patch that makes Kconfig print a warning in this case has been
submitted separately:
http://www.spinics.net/lists/linux-kbuild/msg15566.html
Signed-off-by: Ulf Magnusson <ulfalizer@...il.com>
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 78cb246..3c1faaa 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1033,7 +1033,7 @@ endif
choice
prompt "Compiler optimization level"
- default CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE
+ default CC_OPTIMIZE_FOR_PERFORMANCE
config CC_OPTIMIZE_FOR_PERFORMANCE
bool "Optimize for performance"
--
2.7.4
Powered by blists - more mailing lists