From: Pavel Machek <pavel@suse.cz>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
Parag Warudkar <parag.lkml@gmail.com>, Greg KH <gregkh@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andreas Gruenbacher <agruen@suse.de>,
Jeff Mahoney <jeffm@suse.de>
Subject: config_experimental was Re: [patch 00/04] RFC: Staging tree (drivers/staging)
Date: Mon, 6 Oct 2008 17:11:51 +0200 [thread overview]
Message-ID: <20081006151151.GE1380@ucw.cz> (raw)
In-Reply-To: <20080925105320.ef70065b.randy.dunlap@oracle.com>
Hi!
> > > > How? TAINT_EXPERIMENTAL (I'll stick to that, thanks :) and
> > > > CONFIG_EXPERIMENTAL are no different - neither to users nor to
> > > > developers. Here is why -
> > > > Both try to do the same thing - let people use the drivers on their
> > > > own risk (as if the stable ones are developer's risk - but let's keep
> > > > it aside for the moment) and give developers a chance to keep the code
> > > > in sync with mainline and improve it per user problem reports or
> > > > generally make it better.
> > > >
> > > Uhm.. not quite. As the one that proposed the flag in the first place,
> > > perhaps it helps to cover the rationale (although Greg seems to have
> > > mostly covered that already).
> > >
> > > EXPERIMENTAL today is pretty damn meaningless. What it tends to mean in
> >
> > then it would be better if Greg/someone cleaned up the current tree's
> > problems instead of introducing more CRAP under a different name.
> > Oh well, his mind is already made up and I know how difficult it is to
> > change it.
>
> I shouldn't have said that last sentence. I apologize to Greg.
>
> ISTM that the real problems are (a) it's easier to introduce new staging/crap
> than it is to fix EXPERIMENTAL and (b) no one wants to try to fix EXPERIMENTAL.
>
I do believe that staging != experimental.
experimental == 'good enough code architecture-wise, needs more
testing, coding style is ok'
staging == 'don't look at this after lunch' (at least parts are bad).
Now... I guess someone could go over supported drivers in enterprise
distro, and remove experimental from all of them in mainline...?
Distros pay some attetion to what code they are willing to support...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-10-07 13:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080924224638.514504825@mini.kroah.org>
2008-09-24 23:00 ` [patch 00/04] RFC: Staging tree (drivers/staging) Greg KH
2008-09-24 23:01 ` [patch 01/04] Staging: add TAINT_CRAP for all drivers/staging code Greg KH
2008-09-24 23:01 ` [patch 02/04] Staging: add TAINT_CRAP flag to drivers/staging modules Greg KH
2008-09-24 23:01 ` [patch 04/04] USB: add princeton instruments usb camera driver Greg KH
2008-09-24 23:01 ` [patch 03/04] Staging: add Kconfig entries and Makefile infrastructure Greg KH
2008-09-24 23:39 ` [patch 00/04] RFC: Staging tree (drivers/staging) Parag Warudkar
2008-09-25 1:03 ` Randy Dunlap
2008-09-25 2:06 ` Greg KH
2008-09-25 2:06 ` Greg KH
2008-09-25 2:59 ` Parag Warudkar
2008-09-25 4:21 ` Greg KH
2008-09-25 11:02 ` Parag Warudkar
2008-09-25 20:53 ` Greg KH
2008-09-25 21:40 ` Parag Warudkar
2008-09-25 22:04 ` Greg KH
2008-09-25 22:22 ` Parag Warudkar
2008-09-26 18:36 ` Stefan Richter
2008-09-26 20:11 ` Parag Warudkar
2008-09-26 20:19 ` Greg KH
2008-09-26 20:56 ` Parag Warudkar
2008-09-26 22:03 ` Greg KH
2008-09-26 21:00 ` Leon Woestenberg
2008-09-26 22:04 ` Greg KH
2008-09-26 20:39 ` Stefan Richter
2008-09-26 20:47 ` Parag Warudkar
2008-09-26 22:46 ` Stefan Richter
2008-09-25 5:27 ` Paul Mundt
2008-09-25 14:49 ` Randy Dunlap
2008-09-25 17:53 ` Randy Dunlap
2008-09-25 20:48 ` Greg KH
2008-09-25 21:04 ` Randy Dunlap
2008-09-25 21:51 ` Stefan Richter
2008-10-06 15:11 ` Pavel Machek [this message]
2008-10-09 21:01 ` Adrian Bunk
2008-10-09 21:08 ` Greg KH
2008-10-09 21:17 ` Andrew Morton
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=20081006151151.GE1380@ucw.cz \
--to=pavel@suse.cz \
--cc=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jeffm@suse.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.lkml@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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