Instead of mentioning CodingStyle as a file, use a reference.
While here, do a minor update, pointing that the same rules
for Kernel 2.6 apply up to the recent versions too.
Signed-off-by: Mauro Carvalho Chehab <mche...@s-opensource.com>
---
Documentation/development-process/SubmittingDrivers.rst | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/development-process/SubmittingDrivers.rst
b/Documentation/development-process/SubmittingDrivers.rst
index 621d17af20fd..e4810fb8f4e2 100644
--- a/Documentation/development-process/SubmittingDrivers.rst
+++ b/Documentation/development-process/SubmittingDrivers.rst
@@ -40,9 +40,9 @@ Linux 2.4:
maintainer does not respond or you cannot find the appropriate
maintainer then please contact Willy Tarreau <w...@1wt.eu>.
-Linux 2.6:
+Linux 2.6 and upper:
The same rules apply as 2.4 except that you should follow linux-kernel
- to track changes in API's. The final contact point for Linux 2.6
+ to track changes in API's. The final contact point for Linux 2.6+
submissions is Andrew Morton.
What Criteria Determine Acceptance
@@ -73,7 +73,8 @@ Interfaces:
Code:
Please use the Linux style of code formatting as documented
- in Documentation/development-process/CodingStyle.rst. If you
have sections of code
+ in :ref:`Documentation/development-process/CodingStyle.rst
<codingStyle>`.
+ If you have sections of code
that need to be in other formats, for example because they
are shared with a windows driver kit and you want to
maintain them just once separate them out nicely and note
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
