From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Adrian Bunk" <bunk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL
Date: Tue, 1 Jan 2008 13:14:13 -0500 [thread overview]
Message-ID: <9e4733910801011014y7ae8c84ch439c56fdb1c4f303@mail.gmail.com> (raw)
In-Reply-To: <20080101173532.1db4019f@the-village.bc.nu>
On 1/1/08, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > I'm not claiming that all EXPERIMENTAL tags were wrong [1], but many
> > were wrong.
>
> So why not fix the wrong tags, and mark smbfs obsolete ?
>
> > Plus the fact that CONFIG_EXPERIMENTAL controlled so many different
> > things with one switch that CONFIG_EXPERIMENTAL=n .config's are really
> > rare.
>
> Agreed
CONFIG_EXPERIMENTAL is way to coarse. I always need to turn it on and
then it loses any value.
Why not encode the drivers status into the driver name so that is is
obvious when you are configuring the kernel?
Like this for a driver name:
Compaq Smart Array 5xxx support (experimental)
Some drivers are already do this:
Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)
Now the status is obvious on an item by item basis.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-01-01 18:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 13:48 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 [this message]
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
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=9e4733910801011014y7ae8c84ch439c56fdb1c4f303@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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
all inboxes | Powered by JetHome®