From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: zippel@linux-m68k.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sam@ravnborg.org
Subject: Re: [PATCH] Allow kconfig to accept overrides
Date: Fri, 12 Oct 2007 15:57:08 -0700 [thread overview]
Message-ID: <20071012155708.d8abd06d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710122341530.16098@fbirervta.pbzchgretzou.qr>
On Fri, 12 Oct 2007 23:44:08 +0200 (CEST) Jan Engelhardt wrote:
> Allow config variables in .config to override earlier ones in the same
> file. In other words,
>
> # CONFIG_SECURITY is not defined
> CONFIG_SECURITY=y
>
> will activate it. This makes it a bit easier to do
>
> (cat original-config myconfig myconfig2 ... >.config)
>
> and run menuconfig as expected.
>
> Previously sent:
> http://lkml.org/lkml/2006/10/25/81
> http://lkml.org/lkml/2007/4/1/175
>
> Signed-off-by: Jan Engelhardt <jengelh@gmx.de>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Roman Zippel <zippel@linux-m68k.org>
> Cc: Randy Dunlap <randy.dunlap@oracle.com>
>
> ---
> scripts/kconfig/confdata.c | 14 +++++---------
> 1 file changed, 5 insertions(+), 9 deletions(-)
>
> #
> # Applies cleanly to 2.6.22/23/git.
> #
> Index: linux-2.6.22.1/scripts/kconfig/confdata.c
> ===================================================================
> --- linux-2.6.22.1.orig/scripts/kconfig/confdata.c
> +++ linux-2.6.22.1/scripts/kconfig/confdata.c
> @@ -170,8 +170,7 @@ load:
> sym->type = S_BOOLEAN;
> }
> if (sym->flags & def_flags) {
> - conf_warning("trying to reassign symbol %s", sym->name);
> - break;
> + conf_warning("override: reassigning to symbol %s", sym->name);
> }
> switch (sym->type) {
> case S_BOOLEAN:
> @@ -210,8 +209,7 @@ load:
> sym->type = S_OTHER;
> }
> if (sym->flags & def_flags) {
> - conf_warning("trying to reassign symbol %s", sym->name);
> - break;
> + conf_warning("override: reassigning to symbol %s", sym->name);
> }
> switch (sym->type) {
> case S_TRISTATE:
> @@ -288,11 +286,9 @@ load:
> }
> break;
> case yes:
> - if (cs->def[def].tri != no) {
> - conf_warning("%s creates inconsistent choice state", sym->name);
> - cs->flags &= ~def_flags;
> - } else
> - cs->def[def].val = sym;
> + if(cs->def[def].tri != no)
if (
> + conf_warning("override: %s turns state choice", sym->name);
What does that warning message mean? I can't decipher it.
Other than that, it works for me. Thanks.
> + cs->def[def].val = sym;
> break;
> }
> cs->def[def].tri = E_OR(cs->def[def].tri, sym->def[def].tri);
---
~Randy
next prev parent reply other threads:[~2007-10-12 23:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 21:44 [PATCH] Allow kconfig to accept overrides Jan Engelhardt
2007-10-12 21:49 ` Randy Dunlap
2007-10-12 22:10 ` Jan Engelhardt
2007-10-12 22:57 ` Randy Dunlap [this message]
2007-10-12 23:29 ` Jan Engelhardt
2007-10-12 23:32 ` Randy Dunlap
2007-10-13 8:16 ` Stefan Richter
2007-10-13 11:39 ` Jan Engelhardt
2007-10-13 14:01 ` Stefan Richter
2007-10-13 14:15 ` Jan Engelhardt
2007-10-13 16:25 ` Randy Dunlap
2007-10-13 16:36 ` Jan Engelhardt
2007-10-18 13:29 ` Sam Ravnborg
2007-10-18 13:31 ` Jan Engelhardt
2007-10-16 4:29 ` Sam Ravnborg
2007-10-16 5:14 ` Rob Landley
2007-10-16 14:44 ` Jan Engelhardt
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=20071012155708.d8abd06d.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.org \
/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