Commit f830673f6aa28741ff6993deade587c8550c1dd3

Authored by Andres Salomon
Committed by Linus Torvalds
1 parent e4fabad30e

Documentation/development-process: more staging info

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>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Showing 1 changed file with 19 additions and 6 deletions Side-by-side Diff

Documentation/development-process/2.Process
... ... @@ -303,12 +303,25 @@
303 303 See http://lwn.net/Articles/289013/ for more information on this topic, and
304 304 stay tuned; much is still in flux where linux-next is involved.
305 305  
306   -Besides the mmotm and linux-next trees, the kernel source tree now contains
307   -the drivers/staging/ directory and many sub-directories for drivers or
308   -filesystems that are on their way to being added to the kernel tree
309   -proper, but they remain in drivers/staging/ while they still need more
310   -work.
  306 +2.4.1: STAGING TREES
311 307  
  308 +The kernel source tree now contains the drivers/staging/ directory, where
  309 +many sub-directories for drivers or filesystems that are on their way to
  310 +being added to the kernel tree live. They remain in drivers/staging while
  311 +they still need more work; once complete, they can be moved into the
  312 +kernel proper. This is a way to keep track of drivers that aren't
  313 +up to Linux kernel coding or quality standards, but people may want to use
  314 +them and track development.
  315 +
  316 +Greg Kroah-Hartman currently (as of 2.6.36) maintains the staging tree.
  317 +Drivers that still need work are sent to him, with each driver having
  318 +its own subdirectory in drivers/staging/. Along with the driver source
  319 +files, a TODO file should be present in the directory as well. The TODO
  320 +file lists the pending work that the driver needs for acceptance into
  321 +the kernel proper, as well as a list of people that should be Cc'd for any
  322 +patches to the driver. Staging drivers that don't currently build should
  323 +have their config entries depend upon CONFIG_BROKEN. Once they can
  324 +be successfully built without outside patches, CONFIG_BROKEN can be removed.
312 325  
313 326 2.5: TOOLS
314 327