Skip to content

L
linux-davinci
Commit 5b0ed2c6 authored by Xose Vazquez Perez's avatar Xose Vazquez Perez Committed by Linus Torvalds
Browse files
Options

[PATCH] docs: updated some code docs 

Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent 71fabd5e
Show whitespace changes
Inline Side-by-side
Showing with 63 additions and 28 deletions
Documentation/CodingStyle
View file @ 5b0ed2c6
...@@ -444,10 +444,13 @@ ISBN 0-201-61586-X. ...@@ -444,10 +444,13 @@ ISBN 0-201-61586-X.
URL: http://cm.bell-labs.com/cm/cs/tpop/ URL: http://cm.bell-labs.com/cm/cs/tpop/
GNU manuals - where in compliance with K&R and this text - for cpp, gcc, GNU manuals - where in compliance with K&R and this text - for cpp, gcc,
gcc internals and indent, all available from http://www.gnu.org gcc internals and indent, all available from http://www.gnu.org/manual/
WG14 is the international standardization working group for the programming WG14 is the international standardization working group for the programming
language C, URL: http://std.dkuug.dk/JTC1/SC22/WG14/ language C, URL: http://www.open-std.org/JTC1/SC22/WG14/
Kernel CodingStyle, by greg@kroah.com at OLS 2002:
http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/
-- --
Last updated on 16 February 2004 by a community effort on LKML. Last updated on 16 February 2004 by a community effort on LKML.
Documentation/SubmittingDrivers
View file @ 5b0ed2c6
...@@ -27,18 +27,17 @@ Who To Submit Drivers To ...@@ -27,18 +27,17 @@ Who To Submit Drivers To
------------------------ ------------------------
Linux 2.0: Linux 2.0:
No new drivers are accepted for this kernel tree No new drivers are accepted for this kernel tree.
Linux 2.2: Linux 2.2:
No new drivers are accepted for this kernel tree.
Linux 2.4:
If the code area has a general maintainer then please submit it to If the code area has a general maintainer then please submit it to
the maintainer listed in MAINTAINERS in the kernel file. If the the maintainer listed in MAINTAINERS in the kernel file. If the
maintainer does not respond or you cannot find the appropriate maintainer does not respond or you cannot find the appropriate
maintainer then please contact the 2.2 kernel maintainer: maintainer then please contact Marcelo Tosatti
Marc-Christian Petersen <m.c.p@wolk-project.de>. <marcelo.tosatti@cyclades.com>.
Linux 2.4:
The same rules apply as 2.2. The final contact point for Linux 2.4
submissions is Marcelo Tosatti <marcelo.tosatti@cyclades.com>.
Linux 2.6: Linux 2.6:
The same rules apply as 2.4 except that you should follow linux-kernel The same rules apply as 2.4 except that you should follow linux-kernel
...@@ -53,6 +52,7 @@ Licensing: The code must be released to us under the ...@@ -53,6 +52,7 @@ Licensing: The code must be released to us under the
of exclusive GPL licensing, and if you wish the driver of exclusive GPL licensing, and if you wish the driver
to be useful to other communities such as BSD you may well to be useful to other communities such as BSD you may well
wish to release under multiple licenses. wish to release under multiple licenses.
See accepted licenses at include/linux/module.h
Copyright: The copyright owner must agree to use of GPL. Copyright: The copyright owner must agree to use of GPL.
It's best if the submitter and copyright owner It's best if the submitter and copyright owner
...@@ -143,5 +143,13 @@ KernelNewbies: ...@@ -143,5 +143,13 @@ KernelNewbies:
http://kernelnewbies.org/ http://kernelnewbies.org/
Linux USB project: Linux USB project:
http://sourceforge.net/projects/linux-usb/ http://linux-usb.sourceforge.net/
How to NOT write kernel driver by arjanv@redhat.com
http://people.redhat.com/arjanv/olspaper.pdf
Kernel Janitor:
http://janitor.kernelnewbies.org/
--
Last updated on 17 Nov 2005.
Documentation/SubmittingPatches
View file @ 5b0ed2c6
...@@ -78,7 +78,9 @@ Randy Dunlap's patch scripts: ...@@ -78,7 +78,9 @@ Randy Dunlap's patch scripts:
http://www.xenotime.net/linux/scripts/patching-scripts-002.tar.gz http://www.xenotime.net/linux/scripts/patching-scripts-002.tar.gz
Andrew Morton's patch scripts: Andrew Morton's patch scripts:
http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.20 http://www.zip.com.au/~akpm/linux/patches/
Instead of these scripts, quilt is the recommended patch management
tool (see above).
...@@ -97,7 +99,7 @@ need to split up your patch. See #3, next. ...@@ -97,7 +99,7 @@ need to split up your patch. See #3, next.
3) Separate your changes. 3) Separate your changes.
Separate each logical change into its own patch. Separate _logical changes_ into a single patch file.
For example, if your changes include both bug fixes and performance For example, if your changes include both bug fixes and performance
enhancements for a single driver, separate those changes into two enhancements for a single driver, separate those changes into two
...@@ -112,6 +114,10 @@ If one patch depends on another patch in order for a change to be ...@@ -112,6 +114,10 @@ If one patch depends on another patch in order for a change to be
complete, that is OK. Simply note "this patch depends on patch X" complete, that is OK. Simply note "this patch depends on patch X"
in your patch description. in your patch description.
If you cannot condense your patch set into a smaller set of patches,
then only post say 15 or so at a time and wait for review and integration.
4) Select e-mail destination. 4) Select e-mail destination.
...@@ -124,6 +130,10 @@ your patch to the primary Linux kernel developer's mailing list, ...@@ -124,6 +130,10 @@ your patch to the primary Linux kernel developer's mailing list,
linux-kernel@vger.kernel.org. Most kernel developers monitor this linux-kernel@vger.kernel.org. Most kernel developers monitor this
e-mail list, and can comment on your changes. e-mail list, and can comment on your changes.
Do not send more than 15 patches at once to the vger mailing lists!!!
Linus Torvalds is the final arbiter of all changes accepted into the Linus Torvalds is the final arbiter of all changes accepted into the
Linux kernel. His e-mail address is <torvalds@osdl.org>. He gets Linux kernel. His e-mail address is <torvalds@osdl.org>. He gets
a lot of e-mail, so typically you should do your best to -avoid- sending a lot of e-mail, so typically you should do your best to -avoid- sending
...@@ -149,6 +159,9 @@ USB, framebuffer devices, the VFS, the SCSI subsystem, etc. See the ...@@ -149,6 +159,9 @@ USB, framebuffer devices, the VFS, the SCSI subsystem, etc. See the
MAINTAINERS file for a mailing list that relates specifically to MAINTAINERS file for a mailing list that relates specifically to
your change. your change.
Majordomo lists of VGER.KERNEL.ORG at:
<http://vger.kernel.org/vger-lists.html>
If changes affect userland-kernel interfaces, please send If changes affect userland-kernel interfaces, please send
the MAN-PAGES maintainer (as listed in the MAINTAINERS file) the MAN-PAGES maintainer (as listed in the MAINTAINERS file)
a man-pages patch, or at least a notification of the change, a man-pages patch, or at least a notification of the change,
...@@ -378,22 +391,6 @@ See more details on the proper patch format in the following ...@@ -378,22 +391,6 @@ See more details on the proper patch format in the following
references. references.
13) More references for submitting patches
Andrew Morton, "The perfect patch" (tpp).
<http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
Jeff Garzik, "Linux kernel patch submission format."
<http://linux.yyz.us/patch-format.html>
Greg KH, "How to piss off a kernel subsystem maintainer"
<http://www.kroah.com/log/2005/03/31/>
Kernel Documentation/CodingStyle
<http://sosdg.org/~coywolf/lxr/source/Documentation/CodingStyle>
Linus Torvald's mail on the canonical patch format:
<http://lkml.org/lkml/2005/4/7/183>
----------------------------------- -----------------------------------
...@@ -466,3 +463,30 @@ and 'extern __inline__'. ...@@ -466,3 +463,30 @@ and 'extern __inline__'.
Don't try to anticipate nebulous future cases which may or may not Don't try to anticipate nebulous future cases which may or may not
be useful: "Make it as simple as you can, and no simpler." be useful: "Make it as simple as you can, and no simpler."
----------------------
SECTION 3 - REFERENCES
----------------------
Andrew Morton, "The perfect patch" (tpp).
<http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
Jeff Garzik, "Linux kernel patch submission format."
<http://linux.yyz.us/patch-format.html>
Greg Kroah, "How to piss off a kernel subsystem maintainer".
<http://www.kroah.com/log/2005/03/31/>
<http://www.kroah.com/log/2005/07/08/>
<http://www.kroah.com/log/2005/10/19/>
NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!.
<http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2>
Kernel Documentation/CodingStyle
<http://sosdg.org/~coywolf/lxr/source/Documentation/CodingStyle>
Linus Torvald's mail on the canonical patch format:
<http://lkml.org/lkml/2005/4/7/183>
--
Last updated on 17 Nov 2005.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment