* [PATCH 2/2] Documentation: document the staging directory and submission process
@ 2010-10-27 0:02 Andres Salomon
2010-10-29 3:58 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: Andres Salomon @ 2010-10-27 0:02 UTC (permalink / raw)
To: Randy Dunlap; +Cc: linux-doc, Greg Kroah-Hartman, devel, linux-kernel
Document things that I would've liked to have known when submitting a driver
to gregkh for staging.
Signed-off-by: Andres Salomon <dilinger@queued.net>
---
Documentation/development-process/2.Process | 25 +++++++++++++++++++------
1 files changed, 19 insertions(+), 6 deletions(-)
diff --git a/Documentation/development-process/2.Process b/Documentation/development-process/2.Process
index ae8127c..911a451 100644
--- a/Documentation/development-process/2.Process
+++ b/Documentation/development-process/2.Process
@@ -303,12 +303,25 @@ volatility of linux-next tends to make it a difficult development target.
See http://lwn.net/Articles/289013/ for more information on this topic, and
stay tuned; much is still in flux where linux-next is involved.
-Besides the mmotm and linux-next trees, the kernel source tree now contains
-the drivers/staging/ directory and many sub-directories for drivers or
-filesystems that are on their way to being added to the kernel tree
-proper, but they remain in drivers/staging/ while they still need more
-work.
-
+2.4.1: STAGING TREES
+
+The kernel source tree now contains the drivers/staging/ directory, where
+many sub-directories for drivers or filesystems that are on their way to
+being added to the kernel tree live. They remain in drivers/staging while
+they still need more work; once complete, they can be moved into the
+kernel proper. This is a way to keep track of drivers that aren't
+up to Linux kernel coding or quality standards, but people may want to use
+them and track development.
+
+Greg Kroah-Hartman currently (as of 2.6.36) maintains the staging tree.
+Drivers that still need work are sent to him, with each driver having
+its own subdirectory in drivers/staging/. Along with the driver source
+files, a TODO file should be present in the directory as well. The TODO
+file lists the pending work that the driver needs for acceptance into
+the kernel proper, as well as a list of people that should be Cc'd for any
+patches to the driver. Staging drivers that don't currently build should
+have their config entries depend upon CONFIG_BROKEN. Once they can
+be successfully built without outside patches, CONFIG_BROKEN can be removed.
2.5: TOOLS
--
1.7.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 2/2] Documentation: document the staging directory and submission process
2010-10-27 0:02 [PATCH 2/2] Documentation: document the staging directory and submission process Andres Salomon
@ 2010-10-29 3:58 ` Greg KH
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2010-10-29 3:58 UTC (permalink / raw)
To: Andres Salomon; +Cc: Randy Dunlap, linux-doc, devel, linux-kernel
On Tue, Oct 26, 2010 at 05:02:54PM -0700, Andres Salomon wrote:
>
> Document things that I would've liked to have known when submitting a driver
> to gregkh for staging.
>
> Signed-off-by: Andres Salomon <dilinger@queued.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-10-29 4:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-10-27 0:02 [PATCH 2/2] Documentation: document the staging directory and submission process Andres Salomon
2010-10-29 3:58 ` Greg KH
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.