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 16:32:05 -0700 [thread overview]
Message-ID: <471003F5.6050903@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710130127420.31913@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Oct 12 2007 15:57, Randy Dunlap wrote:
>> On Fri, 12 Oct 2007 23:44:08 +0200 (CEST) Jan Engelhardt wrote:
>>
>>> warning("override: %s turns state choice", sym->name);
>> What does that warning message mean? I can't decipher it.
>
> It is when the value of a "choice" kconfig object is changed, for example
> this .config excerpt:
>
> CONFIG_PREEMPT_NONE=y
> # CONFIG_PREEMPT_VOLUNTARY is not set
> # CONFIG_PREEMPT is not set
> # CONFIG_PREEMPT_BKL is not set
> # CONFIG_PREEMPT_NONE is not set
> CONFIG_REEMPT_VOLUNTARY=y
>
>> Other than that, it works for me. Thanks.
>
> /What/ works, the patch, or the tree without the patch? (Note I was
> testing that on 2.6.23.1, not the git head, so if someone silently
> merged things behind me, I might have missed it. Then again, that
> would have probably caused an offset, fuzz or reject, which was not
> the case.)
The patch and me modifying the .config file by hand to cause overrides.
--
~Randy
next prev parent reply other threads:[~2007-10-12 23:33 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
2007-10-12 23:29 ` Jan Engelhardt
2007-10-12 23:32 ` Randy Dunlap [this message]
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=471003F5.6050903@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