public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL
Date: Mon, 26 Nov 2007 12:27:07 +0000	[thread overview]
Message-ID: <20071126122706.GA5167@ucw.cz> (raw)
In-Reply-To: <20071125161631.GA21947@stusta.de>

On Sun 2007-11-25 17:16:31, Adrian Bunk wrote:
> This patch removes the EXPERIMENTAL option and all dependencies on 
> EXPERIMENTAL because they are pointless.
> 
> Complete rationale:
> - Many people and all distributions are currently forced to enable
>   CONFIG_EXPERIMENTAL since the options for many device drivers depend
>   on this option.
>   I have yet to see someone not being able to install his favorite
>   distribution on his computer only because the distribution did choose
>   to disable all SATA drivers with dependencies on EXPERIMENTAL in their
>   kernels...
> - History has shown that often the dependency on EXPERIMENTAL is not
>   removed when the code has proven usable.
>   As an example, is our NFSv4 support really still in an
>   "alpha-test phase" [1], or is it already ready for being used?
>   I don't know the answer in this specific case, but I wouldn't answer
>   "still in an alpha-test phase" only based on the fact that the NFSv4
>   options still depend on EXPERIMENTAL.
> - It might have been differently 10 years ago, but today everything that
>   is available in a released kernel should also be in a usable state.
> 
> [1] quoted from the CONFIG_EXPERIMENTAL help text

I don't think this is good idea. But perhaps 'experimental' should be
removed from stuff that is really stable these days, like SATA?

							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-11-26 16:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 16:16 [2.6 patch] remove CONFIG_EXPERIMENTAL Adrian Bunk
2007-11-26 12:27 ` Pavel Machek [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2007-12-11 22:21 Adrian Bunk
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
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

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=20071126122706.GA5167@ucw.cz \
    --to=pavel@ucw.cz \
    --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