From: Sam Ravnborg <sam@ravnborg.org>
To: Arve Hj?nnev?g <arve@android.com>
Cc: Michal Marek <mmarek@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
JBeulich@novell.com, aris@redhat.com, catalin.marinas@arm.com,
jacmet@sunsite.dk, justinmattock@gmail.com, lizf@cn.fujitsu.com,
ulfalizer.lkml@gmail.com, zippel@linux-m68k.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild: kconfig changes
Date: Sun, 8 Aug 2010 17:57:12 +0200 [thread overview]
Message-ID: <20100808155712.GA4804@merkur.ravnborg.org> (raw)
In-Reply-To: <AANLkTinOWBfsncSZw3bvHa6Mp+eb5dzibKSV15OKgW2M@mail.gmail.com>
On Fri, Aug 06, 2010 at 09:43:24PM -0700, Arve Hj?nnev?g wrote:
> On Fri, Aug 6, 2010 at 9:01 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> >>
> >> This change prevents some the minimal defconfig options from working.
> >> Specifically our usb gadget drivers do not get set.
> >
> > Can you help me reproduce this?
> >
> > I have found an issue with choice values in combination with
> > tristate logic that fails. I hope this is something similar.
> >
>
> It is probably the same problem. The gadget driver that was not set is
> not buildable as a module (it is not in the mainline kernel). If I
> select another gadget driver instead it just gets changed to build as
> a module instead.
>
> If you create a file, arch/arm/configs/test_defconfig with the following:
> CONFIG_MODULES=y
> CONFIG_USB_GADGET=y
> CONFIG_USB_MASS_STORAGE=y
>
> then "make test_defconfig" results in .config having:
> CONFIG_USB_MASS_STORAGE=m
>
> (at least if you are set up to compile for arm)
Thanks Arve.
I have it reproduced now with a simple Kconfig:
$ cat Kconfig
config M
def_bool y
option modules
choice
prompt "choice list"
config A
tristate "a"
config B
tristate "b"
endchoice
$cat defconfig
CONFIG_M=y
CONFIG_A=y
# CONFIG_B is not set
If I do:
$scripts/kconfig/conf --defconfig=defconfig Kconfig
with the above input the resulting .config is OK.
But If I drop the line:
# CONFIG_B is not set
in the defconfig file then I end with CONFIG_A set to m.
And this is not as expected - I cannot see why it should matter
if we specify the value of B or not.
What we see here is that savedefconfig trigger a bug in the
other part of kconfig - a bug which was not exposed before.
The reason why your patch cured it was that we then no
longer triggered the bug (at least I guess so I did not look to close).
I will look into this as time permits. I assume the fix is simple
when I find the reason.
I fear it is in menu_finalize() and that part of kconfig I have
not yet understood.
Sam
next prev parent reply other threads:[~2010-08-08 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 12:51 Michal Marek
2010-08-05 23:33 ` Linus Torvalds
2010-08-06 1:27 ` Justin P. Mattock
2010-08-06 2:08 ` Linus Torvalds
2010-08-06 2:54 ` Justin P. Mattock
2010-08-06 5:13 ` [PATCH] kconfig: fix make oldconfig Sam Ravnborg
2010-08-06 6:02 ` Justin P. Mattock
2010-08-06 10:21 ` Michal Marek
2010-08-06 16:19 ` Linus Torvalds
2010-08-06 17:52 ` Sam Ravnborg
2010-08-06 18:09 ` Linus Torvalds
2010-08-06 19:52 ` Justin P. Mattock
2010-08-06 23:19 ` [GIT] kbuild: kconfig changes Arve Hjønnevåg
2010-08-07 4:01 ` Sam Ravnborg
2010-08-07 4:43 ` Arve Hjønnevåg
2010-08-08 15:57 ` Sam Ravnborg [this message]
2010-08-10 14:04 ` Michal Marek
2010-08-10 14:25 ` Sam Ravnborg
2010-08-11 19:51 ` Sam Ravnborg
2010-08-11 20:34 ` Sam Ravnborg
2010-08-11 23:39 ` Arve Hjønnevåg
2010-08-12 3:45 ` Sam Ravnborg
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=20100808155712.GA4804@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=JBeulich@novell.com \
--cc=aris@redhat.com \
--cc=arve@android.com \
--cc=catalin.marinas@arm.com \
--cc=jacmet@sunsite.dk \
--cc=justinmattock@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mmarek@suse.cz \
--cc=torvalds@linux-foundation.org \
--cc=ulfalizer.lkml@gmail.com \
--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
all inboxes | Powered by JetHome®