Nice work - thanks.
A couple of possible additions:
* Keep lines within 80 columns.
* Be consistent in use of tabs versus spaces. If the
rest of a file is indented using tabs, then any change
you make should be indented the same way, not with
spaces. It is easy to unknowingly introduce spaces in
a patch by cutting and pasting something in one of the
many desktop UI environments that dont preserve tabs
across a cut and paste.
* See also Documentation/kernel-doc-nano-HOWTO.txt for
formatting the documentation for external functions
and data to work with the kernels DocBook automatically
extractable documentation.
* Multiline comments are shown as:
/*
* This is a big comment. It is full of sound
* and fury, signifying nothing. Now is the time
* for all good men to come to the aid of their
* country.
*/
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |