public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ingo Molnar <mingo@elte.hu>,
	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:57:14 +0200	[thread overview]
Message-ID: <20080101145713.GV2360@does.not.exist> (raw)
In-Reply-To: <20080101143022.664e8894@the-village.bc.nu>

On Tue, Jan 01, 2008 at 02:30:22PM +0000, Alan Cox wrote:
> On Tue, 1 Jan 2008 15:26:23 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
> 
> > 
> > * Adrian Bunk <bunk@kernel.org> wrote:
> > 
> > > This patch removes the EXPERIMENTAL option and all dependencies on 
> > > EXPERIMENTAL since they are pointless.
> > 
> > agreed. CONFIG_BROKEN has real use - but CONFIG_EXPERIMENTAL is pretty 
> > pointless in the 90-days kernel development model.
> 
> Then I need a replacement equivalent for the ATA layer and all the other
> drivers using it to indicate stuff that *IS* experimental, or not yet
> known to be highly robust. Drivers are not the same as core code Ingo and
> the world driver writers live in is very different to the one you operate
> in as is clearly shown by this and by the _p discussion.
> 
> Still NAK.  As the alternative is
> 
> CONFIG_ATA_EXPERIMENTAL, CONFIG_NET_EXPERIMENTAL,
> CONFIG_VIDEO_EXPERIMENTAL, ... all being added by developers

But this alternative is actually _better_.

The point is that e.g. a user having to enable CONFIG_ATA_EXPERIMENTAL 
for getting his hardware supported does not necessarily want to see 
options for experimental congestion control algorithms that might be 
made available by CONFIG_NET_EXPERIMENTAL.

> We will also need experimental badly in future when the EU liability
> rules (and probably the US ones in a similar time scale) change so that
> liability applies to software, because then it will be very important to
> clearly label code that is experimental or development code as such.

Whatever that will imply for free software projects is something 
completely different from what our current CONFIG_EXPERIMENTAL
mess does.

> Alan

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


  reply	other threads:[~2008-01-01 14:57 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 [this message]
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=20080101145713.GV2360@does.not.exist \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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