|| ||Greg KH <firstname.lastname@example.org>|
|| ||Linus Torvalds <email@example.com>,
Andrew Morton <firstname.lastname@example.org>|
|| ||[patch 00/04] RFC: Staging tree (drivers/staging)|
|| ||Wed, 24 Sep 2008 16:00:54 -0700|
|| ||email@example.com, Andreas Gruenbacher <firstname.lastname@example.org>,
Jeff Mahoney <email@example.com>|
As we all discussed at the Kernel Summit this past week, I said I would
create a drivers/staging directory and start throwing lots of drivers
that are not of "mergable" status into it.
For those not at the kernel summit, lwn.net has a summary of this
So, here's 4 patches for review/comments that show how this could be
The first 2 patches create a TAINT_CRAP flag and set it for anything
that comes from the drivers/staging/ directory. When a driver from this
directory is loaded into the kernel, the user is warned, and any oops
message that happens also properly shows the "bad" modules.
The 3rd patch creates the drivers/staging/ directory and Kconfig entries
and adds it to the build system.
The 4th patch is an example of a driver that would go into this
directory, along with a driver_name.README file detailing what needs to
be done to this driver for cleanup/fixing, and who to contact about it.
It's also in such bad shape it doesn't even build against the kernel
(I'll fix that up before submitting, all drivers should at least build
So, does this all look good to everyone? Any questions/issues?
Oh, I guess I should add a MAINTAINER entry for this section of the
kernel, so to paraphrase Linus, I now get to be known as the "Maintainer