<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/Documentation/CodingStyle, branch v3.19</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.19</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.19'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2014-12-02T13:55:32Z</updated>
<entry>
<title>CodingStyle: add some more error handling guidelines</title>
<updated>2014-12-02T13:55:32Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2014-12-02T08:59:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ea04036032edda6f771c1381d03832d2ed0f6c31'/>
<id>urn:sha1:ea04036032edda6f771c1381d03832d2ed0f6c31</id>
<content type='text'>
I added a paragraph on choosing label names, and updated the example
code to use a better label name.  I also cleaned up the example code to
more modern style by moving the allocation out of the initializer and
changing the NULL check.

Perhaps the most common type of error handling bug in the kernel is "one
err bugs".  CodingStyle already says that we should "avoid nesting" by
using error labels and one err style error handling tends to have
multiple indent levels, so this was already bad style.  But I've added a
new paragraph explaining how to avoid one err bugs by using multiple
error labels which is, hopefully, more clear.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Acked-by: Julia Lawall &lt;julia.lawall@lip6.fr&gt;
[jc: added GFP_KERNEL to kmalloc() call]
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>CodingStyle: Add a chapter on conditional compilation</title>
<updated>2014-11-03T16:46:02Z</updated>
<author>
<name>Josh Triplett</name>
<email>josh@joshtriplett.org</email>
</author>
<published>2014-10-29T18:15:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=21228a1868692c34ade648dbb0bc3db0069ab551'/>
<id>urn:sha1:21228a1868692c34ade648dbb0bc3db0069ab551</id>
<content type='text'>
Document several common practices and conventions regarding conditional
compilation, most notably the preference for ifdefs in headers rather
than .c files.

Signed-off-by: Josh Triplett &lt;josh@joshtriplett.org&gt;
Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>CodingStyle: fix a minor typo</title>
<updated>2014-08-26T07:35:54Z</updated>
<author>
<name>Raymond L. Rivera</name>
<email>ray.l.rivera@gmail.com</email>
</author>
<published>2014-07-24T09:39:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7c18fd786de3dabc43e0f412dd63080c14fe6e1b'/>
<id>urn:sha1:7c18fd786de3dabc43e0f412dd63080c14fe6e1b</id>
<content type='text'>
There was a minor typo in the CodingStyle document where the word 'section'
had been spelled as 'secton'.

Signed-off-by: Raymond L. Rivera &lt;ray.l.rivera@gmail.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>Documentation: expand/clarify debug documentation</title>
<updated>2014-06-04T23:54:17Z</updated>
<author>
<name>Dan Streetman</name>
<email>ddstreet@ieee.org</email>
</author>
<published>2014-06-04T23:11:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6e099f557d9c6797c3ee3ee7b5c8cebe543ec1cc'/>
<id>urn:sha1:6e099f557d9c6797c3ee3ee7b5c8cebe543ec1cc</id>
<content type='text'>
The pr_debug() and related debug print macros all differ from the normal
pr_XXX() macros, in that the normal ones print unconditionally, while
the debug macros are compiled out unless DEBUG is defined or
CONFIG_DYNAMIC_DEBUG is set.  This isn't obvious, and the only way to
find this out is either to review the actual printk.h code or to read
CodingStyle, and the message there doesn't highlight the fact.

Change Documentation/CodingStyle to clearly indicate that pr_debug() and
related debug printing macros behave differently than all other pr_XXX()
macros, and attempt to clarify when and where the different debug
printing methods might be used.

Add short comment to printk.h above the pr_XXX() macros indicating that
while these macros print unconditionally, pr_debug() does not.

Signed-off-by: Dan Streetman &lt;ddstreet@ieee.org&gt;
Cc: Joe Perches &lt;joe@perches.com&gt;
Cc: Fabian Frederick &lt;fabf@skynet.be&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Documentation/CodingStyle: allow multiple return statements per function</title>
<updated>2013-07-03T23:08:01Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2013-07-03T22:08:08Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b57a0505e750b3d7b2d39e9823b276d8ca1a08fe'/>
<id>urn:sha1:b57a0505e750b3d7b2d39e9823b276d8ca1a08fe</id>
<content type='text'>
A surprising number of newbies interpret this section to mean that only
one return statement is allowed per function.  Part of the problem is that
the "one return statement per function" rule is an actual style guideline
that people are used to from other projects.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Cc: Eduardo Valentin &lt;eduardo.valentin@ti.com&gt;
Cc: Rob Landley &lt;rob@landley.net&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Documentation: remove depends on CONFIG_EXPERIMENTAL</title>
<updated>2013-01-11T19:38:03Z</updated>
<author>
<name>Kees Cook</name>
<email>keescook@chromium.org</email>
</author>
<published>2012-10-02T18:16:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=0335cb469ad4ab3072a4246ceb0573483fcee5bf'/>
<id>urn:sha1:0335cb469ad4ab3072a4246ceb0573483fcee5bf</id>
<content type='text'>
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.

CC: Rob Landley &lt;rob@landley.net&gt;
CC: Jiri Kosina &lt;jkosina@suse.cz&gt;
CC: Masanari Iida &lt;standby24x7@gmail.com&gt;
CC: Jason Wessel &lt;jason.wessel@windriver.com&gt;
CC: Richard L Maliszewski &lt;richard.l.maliszewski@intel.com&gt;
CC: Gang Wei &lt;gang.wei@intel.com&gt;
CC: Shane Wang &lt;shane.wang@intel.com&gt;
CC: Harry Wei &lt;harryxiyou@gmail.com&gt;
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Acked-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
</content>
</entry>
<entry>
<title>CodingStyle: add networking specific block comment style</title>
<updated>2012-10-05T18:04:59Z</updated>
<author>
<name>Joe Perches</name>
<email>joe@perches.com</email>
</author>
<published>2012-10-05T00:13:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c4ff1b5f8bf09d77d7329cbff224f0237646c90e'/>
<id>urn:sha1:c4ff1b5f8bf09d77d7329cbff224f0237646c90e</id>
<content type='text'>
The block comment style in net/ and drivers/net is non-standard.
Document it.

Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Cc: "Allan, Bruce W" &lt;bruce.w.allan@intel.com&gt;
Cc: Andy Whitcroft &lt;apw@canonical.com&gt;
Cc: David Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>CodingStyle: add kmalloc_array() to memory allocators</title>
<updated>2012-06-01T00:49:26Z</updated>
<author>
<name>Xi Wang</name>
<email>xi.wang@gmail.com</email>
</author>
<published>2012-05-31T23:26:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=15837294d4ce717f69942f7366e99d4d1d3d9923'/>
<id>urn:sha1:15837294d4ce717f69942f7366e99d4d1d3d9923</id>
<content type='text'>
Add the new kmalloc_array() to the list of general-purpose memory
allocators in chapter 14.

Signed-off-by: Xi Wang &lt;xi.wang@gmail.com&gt;
Acked-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Acked-by: Pekka Enberg &lt;penberg@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Documentation: CodingStyle: add inline assembly guidelines</title>
<updated>2012-03-30T23:03:15Z</updated>
<author>
<name>Josh Triplett</name>
<email>josh@joshtriplett.org</email>
</author>
<published>2012-03-30T20:37:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9a7c48b7c3d58835b3a91d86c55e0ae77d15ddd5'/>
<id>urn:sha1:9a7c48b7c3d58835b3a91d86c55e0ae77d15ddd5</id>
<content type='text'>
Signed-off-by: Josh Triplett &lt;josh@joshtriplett.org&gt;
Signed-off-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Documentation: update CodingStyle use of braces</title>
<updated>2011-11-04T19:01:47Z</updated>
<author>
<name>Antonio Ospite</name>
<email>ospite@studenti.unina.it</email>
</author>
<published>2011-11-04T18:22:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b218ab0a5af943441e1daa7dc811874ecd409229'/>
<id>urn:sha1:b218ab0a5af943441e1daa7dc811874ecd409229</id>
<content type='text'>
After commit 38829dc9d7b4 ("Documentation/CodingStyle: flesh out if-else
examples") highlight that if _only_one_ branch of a conditional
statement is a single statement, then braces are to be used on both
branches.

Signed-off-by: Antonio Ospite &lt;ospite@studenti.unina.it&gt;
Signed-off-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
