[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48A18F7B.6040809@keyaccess.nl>
Date: Tue, 12 Aug 2008 15:26:19 +0200
From: Rene Herman <rene.herman@...access.nl>
To: Adrian Bunk <bunk@...nel.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>, fritz@...n4linux.de,
kkeil@...e.de, isdn4linux@...tserv.isdn4linux.de,
linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: [PATCH] ISDN: make ICN not auto-grab port 0x320
On 12-08-08 15:08, Adrian Bunk wrote:
> On Mon, Aug 11, 2008 at 10:30:43PM -0700, Andrew Morton wrote:
>> I think the boot option is the way, if at all.
>>
>> Because the config option isn't very usable. What's to stop someone
>> from doing `make allyesconfig' and then menually editing the .config so
>> it's no longer truly an allyesconfig .config?
>>
>> otoh, if is't purely a manual setting rather than some automagic thing
>> then it might be workable. CONFIG_INGO :)
>
> Write the required settings into a file and use KCONFIG_ALLCONFIG.
Found those, but seems unable to express the "depends on BROKEN_BOOT if
FOO=y" method that's currently used.
Yes, might admittedly not be considered a huge problem and perhaps we
could just ship an allyes.config (and same allrandom.config) but it's
not nice to spread information about a single symbol over various files
like that.
Currently, we have a tristate that turns into a y/n bool if !MODULES.
What would be real nice here is a tristate that turns into a m/n bool if
!RANDOM, where allyesconfig and randconfig would pre-select RANDOM.
If I'm not mistaken, that's currently not possible...
Rene
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists