From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL
Date: Tue, 1 Jan 2008 16:06:07 +0100 [thread overview]
Message-ID: <20080101150607.GC4434@elte.hu> (raw)
In-Reply-To: <20080101143022.664e8894@the-village.bc.nu>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> [...] As the alternative is
>
> CONFIG_ATA_EXPERIMENTAL, CONFIG_NET_EXPERIMENTAL,
> CONFIG_VIDEO_EXPERIMENTAL, ... all being added by developers
yeah, i'd prefer that. People might be willing to enable an experimental
video driver but not an experimental ATA driver. This global-scope "all
or nothing" CONFIG_EXPERIMENTAL is totally pointless and _no_ distro
uses it in practice.
If it's a pure label via which you want to document things as
experimental then i'd agree with adding the "Warning: experimental code"
to the help section of all the affected Kconfig entries (that way people
would be more likely to actually read that label.)
but i think your suggestion of per-subsystem and/or per-driver quality
levels is superior to that.
Ingo
next prev parent reply other threads:[~2008-01-01 15:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 13:48 [2.6 patch] remove CONFIG_EXPERIMENTAL Adrian Bunk
2008-01-01 14:23 ` Alan Cox
2008-01-01 15:17 ` Adrian Bunk
2008-01-01 16:07 ` Alan Cox
2008-01-01 16:33 ` Adrian Bunk
2008-01-01 17:35 ` Alan Cox
2008-01-01 18:14 ` Jon Smirl
2008-01-02 0:06 ` Adrian Bunk
2008-01-01 14:26 ` Ingo Molnar
2008-01-01 14:30 ` Alan Cox
2008-01-01 14:57 ` Adrian Bunk
2008-01-01 15:06 ` Ingo Molnar [this message]
2008-01-01 18:04 ` Jan Engelhardt
2008-01-10 22:18 ` Ralf Baechle
2008-01-11 10:41 ` Paul Mundt
-- strict thread matches above, loose matches on Subject: below --
2007-12-11 22:21 Adrian Bunk
2007-11-25 16:16 Adrian Bunk
2007-11-26 12:27 ` Pavel Machek
2007-11-26 18:57 ` Adrian Bunk
2007-11-27 3:44 ` Valdis.Kletnieks
2007-11-27 4:34 ` Dave Jones
2007-11-27 6:13 ` Valdis.Kletnieks
2007-11-28 12:38 ` Krzysztof Halasa
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=20080101150607.GC4434@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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