public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	fritz@isdn4linux.de, kkeil@suse.de,
	isdn4linux@listserv.isdn4linux.de, linux-kernel@vger.kernel.org,
	mingo@elte.hu
Subject: Re: [PATCH] ISDN: make ICN not auto-grab port 0x320
Date: Tue, 12 Aug 2008 16:45:14 +0200	[thread overview]
Message-ID: <48A1A1FA.3050105@keyaccess.nl> (raw)
In-Reply-To: <20080812140352.GH13910@cs181140183.pp.htv.fi>


On 12-08-08 16:03, Adrian Bunk wrote:

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

Obviously, and that's what is already being done. The point is that as a 
kconfig intrinsic it doesn't add complexity.

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

There's nothing complex about

config FOO
	modstate "Dafttech Boot Breaker 2000 support"

with a modstate being;

- a tristate when !CONFIG_RANDOM
- an m/n choice otherwise

And note that it's not "single developer use case". Feel how you want 
about anyone, but it's about useful testing being done. It's about 
developers getting bugs reported to them as a result.

Rene.

  reply	other threads:[~2008-08-12 14:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09 17:39 [PATCH] ISDN: make ICN not auto-grab port 0x320 Rene Herman
2008-08-09 20:50 ` Alan Cox
2008-08-11 23:48   ` Andrew Morton
2008-08-12  5:02     ` Rene Herman
2008-08-12  5:30       ` Andrew Morton
2008-08-12 13:08         ` Adrian Bunk
2008-08-12 13:26           ` Rene Herman
2008-08-12 13:43             ` Adrian Bunk
2008-08-12 13:53               ` Rene Herman
2008-08-12 14:03                 ` Adrian Bunk
2008-08-12 14:45                   ` Rene Herman [this message]
2008-08-12 15:23                     ` Adrian Bunk
2008-08-12 13:46             ` Rene Herman

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=48A1A1FA.3050105@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@kernel.org \
    --cc=fritz@isdn4linux.de \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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