From: Michal Marek <mmarek@suse.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig: fix savedefconfig with choice marked optional
Date: Sun, 15 Aug 2010 00:41:08 +0200 [thread overview]
Message-ID: <4C671B84.1090801@suse.cz> (raw)
In-Reply-To: <20100814212900.GA29962@merkur.ravnborg.org>
Dne 14.8.2010 23:29, Sam Ravnborg napsal(a):
> From db5b47421d4e9c2f3a35bc3aaa4a1423b767e00a Mon Sep 17 00:00:00 2001
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Sat, 14 Aug 2010 23:22:16 +0200
> Subject: [PATCH] kconfig: fix savedefconfig with choice marked optional
>
> savedefconfig failed to save the correct minimal config
> when it encountered a choice marked optional.
>
> Consider following minimal configuration:
> $cat Kconfig
> choice
> prompt "choice"
> optional
>
> config A
> bool "a"
>
> config B
> bool "b"
>
> endchoice
>
> $cat .config | grep -v ^#
> CONFIG_A=y
>
> $conf --savedefconfig=defconfig Kconfig
>
> would before this fix result in an empty file, because
> kconfig would assume that CONFIG_A=y is a default value.
> But because the choice is optional the default is that
> both A and B are =n.
>
> Fix so we handle optional choices correct.
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> ---
> scripts/kconfig/confdata.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
Applied to kbuild/kconfg.
Michal
next prev parent reply other threads:[~2010-08-14 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 21:29 [PATCH] kconfig: fix savedefconfig with choice marked optional Sam Ravnborg
2010-08-14 22:41 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-14 23:26 Sedat Dilek
2010-08-15 1:15 ` Sam Ravnborg
2010-08-15 7:07 ` Sedat Dilek
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=4C671B84.1090801@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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