From: Michal Marek <mmarek@suse.cz>
To: Jiafu He <jay@goldhive.com>
Cc: linux-kbuild@vger.kernel.org, Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [PATCH] Kconfig: default m doesn't work for menuconfig/xconfig/gconfig even if CONFIG_MODULES=y
Date: Thu, 17 Dec 2009 22:48:50 +0100 [thread overview]
Message-ID: <4B2AA742.6020603@suse.cz> (raw)
In-Reply-To: <20091216173556.0b50c25debf12a9aa545bf810459b532.9761f5fd4a.wbe@email.secureserver.net>
Jiafu He napsal(a):
> menuconfig/xconfig/gconfig all fails to set tristate CONFIG_ options to
> m even if CONFIG_MODULES=y has been set. The "config" target works,
> though.
On a x86_64, I tried adding
config FOOBAR
tristate "foobar"
default m
---help---
aaa aaa
to init/Kconfig
The I run make menuconfig in an already configured build dir and in an
empty one, in both cases FOOBAR was preset to M. Could you provide a
step-by-step testcase that shows the problem you want to fix?
Thanks!
Michal
>
> Signed-off-by: Jiafu He <jay@goldhive.com>
> -----
> diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
> index b55e72f..9ff712b 100644
> --- a/scripts/kconfig/confdata.c
> +++ b/scripts/kconfig/confdata.c
> @@ -170,8 +170,11 @@ int conf_read_simple(const char *name, int def)
> if (in)
> goto load;
> sym_add_change_count(1);
> - if (!sym_defconfig_list)
> + if (!sym_defconfig_list) {
> + if (modules_sym)
> + sym_calc_value(modules_sym);
> return 1;
> + }
>
> for_all_defaults(sym_defconfig_list, prop) {
> if (expr_calc_value(prop->visible.expr) == no ||
> -----
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-12-17 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 0:35 [PATCH] Kconfig: default m doesn't work for menuconfig/xconfig/gconfig even if CONFIG_MODULES=y Jiafu He
2009-12-17 21:48 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-18 0:55 Jiafu He
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=4B2AA742.6020603@suse.cz \
--to=mmarek@suse.cz \
--cc=jay@goldhive.com \
--cc=linux-kbuild@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.