From: Adrian Bunk <bunk@kernel.org>
To: Rene Herman <rene.herman@keyaccess.nl>
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:43:38 +0300 [thread overview]
Message-ID: <20080812134337.GG13910@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <48A18F7B.6040809@keyaccess.nl>
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
next prev parent reply other threads:[~2008-08-12 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 17:39 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 [this message]
2008-08-12 13:53 ` Rene Herman
2008-08-12 14:03 ` Adrian Bunk
2008-08-12 14:45 ` Rene Herman
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=20080812134337.GG13910@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fritz@isdn4linux.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rene.herman@keyaccess.nl \
/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
all inboxes | Powered by JetHome®