All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	kir@swsoft.com, containers@lists.osdl.org,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	kir@openvz.org, Cedric Le Goater <clg@fr.ibm.com>,
	Pavel Emelyanov <xemul@openvz.org>,
	Sukadev Bhattiprolu <sukadev@us.ibm.com>
Subject: Re: [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2)
Date: Sat, 27 Oct 2007 07:17:24 +0200	[thread overview]
Message-ID: <20071027051724.GR30533@stusta.de> (raw)
In-Reply-To: <m14pgdtbkj.fsf@ebiederm.dsl.xmission.com>

On Fri, Oct 26, 2007 at 10:40:12PM -0600, Eric W. Biederman wrote:
> Adrian Bunk <bunk@kernel.org> writes:
> 
> > There isn't any hard semantics behind what is marked EXPERIMENTAL and 
> > what not. In it's current state, we could even consider removing the 
> > EXPERIMENTAL option and all dependencies on EXPERIMENTAL.
> 
> Well I do know at least some of the things that depend on experimental
> are legitimate.
> 
> I wonder if the problem is that we don't police experimental well
> enough.
> 
> > Currently CONFIG_EXPERIMENTAL=n would cost a distribution a three digit 
> > number of device drivers plus several features like e.g. NFSv4.
> 
> I can see a distribution carefully cherry picking things, that the
> have an intimate knowledge about out of experimental but it doesn't
> sound right for taking things out of EXPERIMENTAL to be routine.
> 
> I know I'm a little slow about getting around to it but when ever I
> have a feature that isn't EXPERIMENTAL anymore I remove the tag.

Part of the picture might be that code that was included into the kernel 
usually is in a state that it works at least most time for most of the 
people.

And when you think about distributions, it's hard to imagine why a 
distribution should not enable more or less all EXPERIMENTAL device 
drivers - an EXPERIMENTAL driver is much better than no driver for this 
hardware at all.

> Eric

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:[~2007-10-27  5:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 20:58 [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2) Kir Kolyshkin
2007-10-26 21:59 ` Eric W. Biederman
2007-10-26 21:59   ` Eric W. Biederman
2007-10-27  0:24   ` Adrian Bunk
2007-10-27  1:31     ` Eric W. Biederman
2007-10-27  2:04       ` Adrian Bunk
2007-10-27  2:18         ` Andrew Morton
2007-10-27  3:46           ` Eric W. Biederman
2007-10-27  4:03             ` Adrian Bunk
2007-10-27  4:40               ` Eric W. Biederman
2007-10-27  5:17                 ` Adrian Bunk [this message]
     [not found]             ` <m18x5pte18.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-10-27  4:40               ` Andrew Morton
2007-10-27  4:40                 ` Andrew Morton
     [not found]                 ` <20071026214046.c61e248d.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2007-10-27  7:41                   ` Eric W. Biederman
2007-10-27  7:41                     ` Eric W. Biederman
2007-10-29 18:05             ` Cedric Le Goater
2007-10-29 19:11               ` Eric W. Biederman
2007-10-28 16:12       ` Jeremy Fitzhardinge
2007-10-28 17:00         ` Adrian Bunk
2007-10-28 18:31           ` Eric W. Biederman
2007-10-29 10:13             ` Cedric Le Goater
2007-10-29 18:08               ` Eric W. Biederman
2007-10-26 22:34 ` Eric W. Biederman
2007-10-26 22:34   ` Eric W. Biederman

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=20071027051724.GR30533@stusta.de \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=kir@openvz.org \
    --cc=kir@swsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sukadev@us.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.