Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c

From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: "Roman Zippel" <zippel@linux-m68k.org>,
	"Mauro Carvalho Chehab" <mchehab@infradead.org>,
	"Oliver Neukum" <oneukum@suse.de>,
	linux-usb-devel@lists.sourceforge.net,
	video4linux-list@redhat.com,
	"Toralf F�rster" <toralf.foerster@gmx.de>,
	luca.risolia@studio.unibo.it, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
Date: Sat, 23 Jun 2007 01:47:40 +0530	[thread overview]
Message-ID: <a781481a0706221317q3dd49905j8773b2f8a96ad63b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706221842220.26568@fbirervta.pbzchgretzou.qr>

Hi Jan,

On 6/22/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Jun 22 2007 18:24, Roman Zippel wrote:
> >
> >> There have been discussions to remove the default-ys again, I've sent a patch
> >> [http://lkml.org/lkml/2007/5/12/216], but nothing happened.
> >>
> >> So, should all affected menuconfigs be transformed into tristates, what
> >> do you think, Roman? Let me know so I can cook up a patch (hopefully
> >> before 2.6.22) should they become tristate.
> >
> >Using bool is clearly a bug and I'd prefer if it removed the defaults as
> >well.
>
> What I don't quite understand is, that CONFIG_CRYPTO is also a bool,
> its subparts are tristates however, and there is no problem involved
> with these.

That's because neither CONFIG_CRYPTO nor any of the crypto modules
depend on another symbol that is itself tristate (and hence can be modular),
which is the case with all the problematic cases that have been posted to
lkml lately.

Satyam