From: Josh Triplett <josh@joshtriplett.org>
To: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Michal Marek <mmarek@suse.cz>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
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>
Subject: [PATCH 1/1] kconfig: tinyconfig: x86: List disabled choices to avoid warning
Date: Mon, 18 Jul 2016 12:32:07 -0700 [thread overview]
Message-ID: <20160718193206.GA20396@x> (raw)
In-Reply-To: <20160718160035.3062818-1-arnd@arndb.de>
The Kconfig machinery used to power tinyconfig produces a warning like
this when changing a "choice" option without explicitly disabling the
other choices:
.config:965:warning: override: NOHIGHMEM changes choice state
Expand arch/x86/configs/tiny.config to add entries disabling the other
two choices, to eliminate this warning. (Doing so then introduces a
different form of warning for changing any option at all, but that needs
fixing in the underlying config merge machinery.)
Based on a similar change from Arnd Bergmann for the
architecture-independent tiny.config.
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Reported-by: Arnd Bergmann <arnd@arndb.de>
---
arch/x86/configs/tiny.config | 2 ++
1 file changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/x86/configs/tiny.config b/arch/x86/configs/tiny.config
index 4e2ecfa..4b429df 100644
--- a/arch/x86/configs/tiny.config
+++ b/arch/x86/configs/tiny.config
@@ -1 +1,3 @@
CONFIG_NOHIGHMEM=y
+# CONFIG_HIGHMEM4G is not set
+# CONFIG_HIGHMEM64G is not set
--
git-series 0.8.3
next prev parent reply other threads:[~2016-07-18 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 16:00 [PATCH] kconfig: tinyconfig: provide whole choice blocks to avoid warnings Arnd Bergmann
2016-07-18 19:31 ` Josh Triplett
2016-07-18 19:50 ` Arnd Bergmann
2016-07-18 19:32 ` Josh Triplett [this message]
2016-07-21 1:21 ` 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=20160718193206.GA20396@x \
--to=josh@joshtriplett.org \
--cc=arnd@arndb.de \
--cc=dvhart@linux.intel.com \
--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