From: Randy Dunlap <randy.dunlap@oracle.com>
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: Re: [patch 00/04] RFC: Staging tree (drivers/staging)
Date: Thu, 25 Sep 2008 10:53:20 -0700 [thread overview]
Message-ID: <20080925105320.ef70065b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080925074923.4845005b.randy.dunlap@oracle.com>
On Thu, 25 Sep 2008 07:49:23 -0700 Randy Dunlap wrote:
> On Thu, 25 Sep 2008 14:27:26 +0900 Paul Mundt wrote:
>
> > On Wed, Sep 24, 2008 at 10:59:03PM -0400, Parag Warudkar wrote:
> > > On Wed, Sep 24, 2008 at 10:06 PM, Greg KH <gregkh@suse.de> wrote:
> > > > No, this is much different from EXPERIMENTAL. That flag is pretty much
> > > > useless right now. This is for a temporary landing place for drivers
> > > > that are not good enough to be merged, yet are useful enough for some
> > > > people to use.
> > >
> > > 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.
---
~Randy
next prev parent reply other threads:[~2008-09-25 17:54 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 ` 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 [this message]
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 ` config_experimental was " Pavel Machek
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=20080925105320.ef70065b.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--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=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
Powered by JetHome