Re: [patch 00/04] RFC: Staging tree (drivers/staging)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Greg KH
Date: Wednesday, September 24, 2008 - 7:06 pm

On Wed, Sep 24, 2008 at 07:39:42PM -0400, Parag Warudkar 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.

Examples of this is the USB driver I posted, some network drivers that
are in -staging that only work on x86 boxes, and drivers that have
userspace interfaces that are "wrong" and need to be changed (reading
files from /etc is one example.)

All of those types of drivers are not capable of being merged today, and
EXPERIMENTAL doesn't mean anything there.

Also, api changes do not have to propagate into the drivers/staging/
directory.  I'll work to keep up with them, keeping everything working
properly, just like I have been with the external -staging tree.  This
is just pushing it into the tree to give it much wider exposure and draw
from more developers makeing it easier to give them the proper credit
for this clean-up work.


Why, that word is only internal, nothing outside of the kernel sees that
flag at all, no user will ever know this.

And if we leave it as TAINT_CRAP, and a developer sees it, perhaps it
will cause them to make their code cleaner next time around :)


I can easily add a "no_crap" flag to the command line.  Oops, there's
that word going out to userspace, how about "no_staging"?


This keeps these kinds of drivers in one place, obvious to all that work
needs to be done, and userspace interfaces can, and usually will change
for such drivers.

I think the boat has left on making EXPERIMENTAL mean anything anymore,
but if you or anyone else wants to clean up the tree, and free it up,
then I would reconsider using it here instead.  But you can't start
making it something that means more than it does today, as I can easily
see that breaking systems that currently rely on those drivers.

thanks,

greg k-h
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Wed Sep 24, 4:39 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Randy Dunlap, (Wed Sep 24, 6:03 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Greg KH, (Wed Sep 24, 7:06 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Wed Sep 24, 7:59 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Paul Mundt, (Wed Sep 24, 10:27 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Thu Sep 25, 4:02 am)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Randy Dunlap, (Thu Sep 25, 7:49 am)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Randy Dunlap, (Thu Sep 25, 10:53 am)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Randy Dunlap, (Thu Sep 25, 2:04 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Thu Sep 25, 2:40 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Stefan Richter, (Thu Sep 25, 2:51 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Thu Sep 25, 3:22 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Stefan Richter, (Fri Sep 26, 11:36 am)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Fri Sep 26, 1:11 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Stefan Richter, (Fri Sep 26, 1:39 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Fri Sep 26, 1:47 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Parag Warudkar, (Fri Sep 26, 1:56 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Leon Woestenberg, (Fri Sep 26, 2:00 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Stefan Richter, (Fri Sep 26, 3:46 pm)
Re: [patch 00/04] RFC: Staging tree (drivers/staging), Andrew Morton, (Thu Oct 9, 2:17 pm)