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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080812140352.GH13910@cs181140183.pp.htv.fi>
Date:	Tue, 12 Aug 2008 17:03:52 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Rene Herman <rene.herman@...access.nl>
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 Tue, Aug 12, 2008 at 03:53:33PM +0200, Rene Herman wrote:
> On 12-08-08 15:43, Adrian Bunk wrote:
>
>>> 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.
>
> Oh, how very, very important. s/RANDOM/!SPECIFIC/ then (and I meant "if  
> RANDOM" ofcourse).
>
> The point is just that such a tristate would be a one-stop mark for  
> drivers/options that you want to be  specifically selected for builtin  
> use since they're not necessarily expected to boot on general PCs.

The part of what you want that is AFAIK not possible with the current 
kconfig is the "allyesconfig and randconfig would pre-select".

The actual dependencies on such an option could trivially be expressed 
the way you want it.

But I'm trying to make the kconfig dependencies more robust by making 
them less complex, and making them more complex for this developer-only
use case is nonsense.

Even more considering that the developer who gave the initial list of 
variables is the same who always spreads FUD about kconfig when the 
complex dependencies break...

> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/