From: Michal Marek <mmarek@suse.cz>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
linux-kbuild@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig: fix new choices being skipped upon config update
Date: Thu, 26 Jan 2012 11:06:43 +0100 [thread overview]
Message-ID: <4F2125B3.4070000@suse.cz> (raw)
In-Reply-To: <20120126092603.GQ6305@pengutronix.de>
On 26.1.2012 10:26, Uwe Kleine-König wrote:
> On Mon, Jan 23, 2012 at 05:29:05PM -0500, Arnaud Lacombe wrote:
[...]
>> will not cause the choice to be considered as NEW, and thus not be asked. The
>> cause of this behavior is that choice's novelty are computed statically right
>> after the saved configuration has been read. At this point, the new dependency's
>> value is still unknown and asserted to be `no'. Moreover, no update to this
>> decision is made afterward.
>>
>> Correct this by dynamically evaluating a choice's novelty, and removing the
>> static evaluation.
>>
>> Cc: linux-kbuild@vger.kernel.org
>> Cc: LKML <linux-kernel@vger.kernel.org>,
>> Cc: Michal Marek <mmarek@suse.cz>
>> Cc: Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>
>> Reported-by: Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>
> Tested-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Thanks, applied to kbuild.git#kconfig.
> (Please note the umlaut o in my name. If you have problems with that,
> please at least write Kleine-Koenig.)
Fixed.
Michal
prev parent reply other threads:[~2012-01-26 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 16:40 inconvenience when hand editing DEBUG_LL in .config Uwe Kleine-König
2012-01-20 19:27 ` Russell King - ARM Linux
2012-01-20 23:34 ` Uwe Kleine-König
2012-01-20 20:31 ` Arnaud Lacombe
2012-01-23 22:29 ` [PATCH] kconfig: fix new choices being skipped upon config update Arnaud Lacombe
2012-01-26 9:26 ` Uwe Kleine-König
2012-01-26 10:06 ` Michal Marek [this message]
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=4F2125B3.4070000@suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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