Re: [PATCH] ISDN: make ICN not auto-grab port 0x320

[Adrian Bunk]

On Tue, Aug 12, 2008 at 03:26:19PM +0200, Rene Herman wrote:
> 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.

The dependencies we express in kconfig are already pretty complicated, 
and that is continuously causing problems.

Stuffing more stuff into kconfig for such an exotic developer-only use 
case is not a good idea.

And as already said, tomorrow someone might want to boot an allyesconfig 
kernel on a Pentium-MMX...

> 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.

allyesconfig is not random.

> If I'm not mistaken, that's currently not possible...
> 
> Rene

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/