From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Andreas Gruenbacher <agruen@suse.de>,
Jeff Mahoney <jeffm@suse.de>
Subject: [patch 00/04] RFC: Staging tree (drivers/staging)
Date: Wed, 24 Sep 2008 16:00:54 -0700 [thread overview]
Message-ID: <20080924230054.GA27730@suse.de> (raw)
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
session at:
http://www.lwn.net/Articles/298570/
So, here's 4 patches for review/comments that show how this could be
done.
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
kernel :)
(I'll fix that up before submitting, all drivers should at least build
properly...)
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
of Crap".
thanks,
greg k-h
next reply other threads:[~2008-09-24 23:04 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 [this message]
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 ` 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=20080924230054.GA27730@suse.de \
--to=gregkh@suse.de \
--cc=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeffm@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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