From: Arnd Bergmann <arnd@arndb.de>
To: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Cc: Michal Marek <mmarek@suse.cz>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Josh Triplett <josh@joshtriplett.org>,
Darren Hart <dvhart@linux.intel.com>,
kernel-build-reports@lists.linaro.org,
Thiago Macieira <thiago.macieira@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH] kconfig: tinyconfig: provide whole choice blocks to avoid warnings
Date: Mon, 18 Jul 2016 18:00:23 +0200 [thread overview]
Message-ID: <20160718160035.3062818-1-arnd@arndb.de> (raw)
Using "make tinyconfig" produces a couple of annoying warnings that show up
for build test machines all the time:
.config:966:warning: override: NOHIGHMEM changes choice state
.config:965:warning: override: SLOB changes choice state
.config:963:warning: override: KERNEL_XZ changes choice state
.config:962:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state
.config:933:warning: override: SLOB changes choice state
.config:930:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state
.config:870:warning: override: SLOB changes choice state
.config:868:warning: override: KERNEL_XZ changes choice state
.config:867:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state
I've made a previous attempt at fixing them and we discussed a number of
alternatives.
I tried changing the Makefile to use "merge_config.sh -n $(fragment-list)"
but couldn't get that to work properly.
This is yet another approach, based on the observation that we do want
to see a warning for conflicting 'choice' options, and that we can simply
make them non-conflicting by listing all other options as disabled.
This is a trivial patch that we can apply independent of plans for other
changes.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Link: https://storage.kernelci.org/mainline/v4.7-rc6/x86-tinyconfig/build.log
https://patchwork.kernel.org/patch/9212749/
---
kernel/configs/tiny.config | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/kernel/configs/tiny.config b/kernel/configs/tiny.config
index c2de56ab0fce..3eeade4d876d 100644
--- a/kernel/configs/tiny.config
+++ b/kernel/configs/tiny.config
@@ -1,4 +1,12 @@
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
+# CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE is not set
CONFIG_KERNEL_XZ=y
+# CONFIG_KERNEL_GZIP is not set
+# CONFIG_KERNEL_BZIP2 is not set
+# CONFIG_KERNEL_LZMA is not set
+# CONFIG_KERNEL_LZO is not set
+# CONFIG_KERNEL_LZ4 is not set
CONFIG_OPTIMIZE_INLINING=y
+# CONFIG_SLUB is not set
+# CONFIG_SLAB is not set
CONFIG_SLOB=y
--
2.9.0
next reply other threads:[~2016-07-18 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 16:00 Arnd Bergmann [this message]
2016-07-18 19:31 ` [PATCH] kconfig: tinyconfig: provide whole choice blocks to avoid warnings Josh Triplett
2016-07-18 19:50 ` Arnd Bergmann
2016-07-18 19:32 ` [PATCH 1/1] kconfig: tinyconfig: x86: List disabled choices to avoid warning Josh Triplett
2016-07-21 1:21 ` [PATCH] kconfig: tinyconfig: provide whole choice blocks to avoid warnings Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160718160035.3062818-1-arnd@arndb.de \
--to=arnd@arndb.de \
--cc=dvhart@linux.intel.com \
--cc=josh@joshtriplett.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=thiago.macieira@intel.com \
--cc=yamada.masahiro@socionext.com \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox