<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in CodingStyle</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>08a9a8d4 - doc: re-add CodingStyle and SubmittingPatches</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#08a9a8d4</link>
        <description>doc: re-add CodingStyle and SubmittingPatchesThose files got moved to Documentation/process, but as they&apos;re verywell known files, add pointers to their new locations.PS.: I opted to not merge this patch with the previous onein order to make the diff of the previous one more consistent,as it will show only renames.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Tue, 18 Oct 2016 11:22:55 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;</dc:creator>
    </item>
<item>
        <title>79c70c30 - docs: Remove space-before-label guidance from CodingStyle</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#79c70c30</link>
        <description>docs: Remove space-before-label guidance from CodingStyleRecent discussion has made it clear that there is no community consensus onthis particular rule.  Remove it now, lest it inspire yet another set ofunwanted &quot;cleanup&quot; patches.This partially reverts 865a1caa4b6b (CodingStyle: Clarify and completechapter 7).Cc: Jean Delvare &lt;jdelvare@suse.de&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Wed, 21 Sep 2016 21:46:18 +0000</pubDate>
        <dc:creator>Jonathan Corbet &lt;corbet@lwn.net&gt;</dc:creator>
    </item>
<item>
        <title>609d99a3 - Documentation/HOWTO: add cross-references to other documents</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#609d99a3</link>
        <description>Documentation/HOWTO: add cross-references to other documentsAdd cross references for the documents mentioned at HOWTO andare under the Documentation/ directory, using the ReST notation.It should be noticed that HOWTO also mentions the /README file.We opted to not touch it, for now, as making it build onSphinx would require it to be moved to a Documentation/foodirectory.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 19 Sep 2016 11:07:56 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;</dc:creator>
    </item>
<item>
        <title>3772ec4a - Documentation/CodingStyle: use the .. note:: markup where needed</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#3772ec4a</link>
        <description>Documentation/CodingStyle: use the .. note:: markup where neededThere are two places there where there are notes that shouldbe highlighted. So, use the ReST note markup for such texts.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 19 Sep 2016 11:07:47 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;</dc:creator>
    </item>
<item>
        <title>5d628b45 - Documentation/CodingStyle: replace underline markups</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#5d628b45</link>
        <description>Documentation/CodingStyle: replace underline markupsSphinx doesn&apos;t accept underline markups by purpose.While there are ways to support underline via CSS, this won&apos;tbe portable with non-html outputs.As we want CodingStyle to do emphasis, replace _foo_ by **foo**,using bold emphasis.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 19 Sep 2016 11:07:46 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;</dc:creator>
    </item>
<item>
        <title>b1a3459b - Documentation/CodingStyle: use the proper tag for verbatim font</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#b1a3459b</link>
        <description>Documentation/CodingStyle: use the proper tag for verbatim fontOn Sphinx/ReST notation, ``foo`` means that foo will be will bemarked as inline literal, effectively making it to be presentedas a monospaced font.As we want this document to be parsed by Sphinx, instead of using&quot;foo&quot;, use ``foo`` for the names that are literal, because it is anusual typographic convention to use monospaced fonts for functionsand language commands on documents, and we&apos;re following suchconvention on the other ReST books.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 19 Sep 2016 11:07:45 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;</dc:creator>
    </item>
<item>
        <title>d8dbbbc5 - Documentation/CodingStyle: Convert to ReST markup</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#d8dbbbc5</link>
        <description>Documentation/CodingStyle: Convert to ReST markup- Fix all chapter identation;- add c blocks where needed;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 19 Sep 2016 11:07:44 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;</dc:creator>
    </item>
<item>
        <title>a78a136f - CodingStyle: Remove &quot;Don&apos;t use C99-style comments&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#a78a136f</link>
        <description>CodingStyle: Remove &quot;Don&apos;t use C99-style comments&quot;Because Linus may still be reading source code on greenbar paperinstead of color terminals with code syntax highlighting andappropriate font decorations.Link: http://lkml.kernel.org/r/CA+55aFyQYJerovMsSoSKS7PessZBr4vNp-3QUUwhqk4A4_jcbg@mail.gmail.comSigned-off-by: Joe Perches &lt;joe@perches.com&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Wed, 13 Jul 2016 00:18:28 +0000</pubDate>
        <dc:creator>Joe Perches &lt;joe@perches.com&gt;</dc:creator>
    </item>
<item>
        <title>865a1caa - CodingStyle: Clarify and complete chapter 7</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#865a1caa</link>
        <description>CodingStyle: Clarify and complete chapter 7Chapter 7 (Centralized exiting of functions) of the coding styledocumentation is unclear at times, and lacks some information (suchas the possibility to indent labels with a single space.) Clarify andcomplete it.Signed-off-by: Jean Delvare &lt;jdelvare@suse.de&gt;Cc: Markus Elfring &lt;elfring@users.sourceforge.net&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 25 Jul 2016 12:29:06 +0000</pubDate>
        <dc:creator>Jean Delvare &lt;jdelvare@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>8ed292fe - docs: deprecate kernel-doc-nano-HOWTO.txt</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#8ed292fe</link>
        <description>docs: deprecate kernel-doc-nano-HOWTO.txtNow that the new Sphinx world order is taking over, the information inkernel-doc-nano-HOWTO.txt is outmoded.  I hate to remove it altogether,since it&apos;s one of those files that people expect to find.  But we can add awarning and fix all the other pointers to it.Reminded-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Wed, 20 Jul 2016 22:43:41 +0000</pubDate>
        <dc:creator>Jonathan Corbet &lt;corbet@lwn.net&gt;</dc:creator>
    </item>
<item>
        <title>32fd52d5 - Documentation/CodingStyle: add space before parenthesis in example macro</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#32fd52d5</link>
        <description>Documentation/CodingStyle: add space before parenthesis in example macroSigned-off-by: Thomas Gardner &lt;tmg@fastmail.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 25 Jan 2016 05:54:39 +0000</pubDate>
        <dc:creator>Thomas Gardner &lt;tmg@fastmail.com&gt;</dc:creator>
    </item>
<item>
        <title>9a2885e6 - Documentation: fix typo in CodingStyle</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#9a2885e6</link>
        <description>Documentation: fix typo in CodingStyleSimple typo: &quot;it&quot; for &quot;is&quot;.Signed-off-by: Manuel P&#233;gouri&#233;-Gonnard &lt;mpg@elzevir.fr&gt;Cc: Trivial Patch Monkey &lt;trivial@kernel.org&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 28 Dec 2015 10:06:55 +0000</pubDate>
        <dc:creator>Manuel P&#233;gouri&#233;-Gonnard &lt;mpg@elzevir.fr&gt;</dc:creator>
    </item>
<item>
        <title>4b10df7f - Documentation: CodingStyle: remove broken links in the References section</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#4b10df7f</link>
        <description>Documentation: CodingStyle: remove broken links in the References sectionRemove 2 broken links for programming reference books in Appendix I. Aftera lookup on an Internet archives web site, it seems that these links havebeen broken for around 3 months. We can then assume that they will not beback up and safely remove them from the documentation.Signed-off-by: Olivier C. Larocque &lt;olivier.c.larocque@gmail.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Fri, 03 Jul 2015 01:33:23 +0000</pubDate>
        <dc:creator>Olivier C. Larocque &lt;olivier.c.larocque@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>df1027ab - Documentation/CodingStyle: fix example macro parenthesis imbalance</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#df1027ab</link>
        <description>Documentation/CodingStyle: fix example macro parenthesis imbalanceCc: Bartosz Golaszewski &lt;bgolaszewski@baylibre.com&gt;Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;Fixes: f2027543b9 (&apos;documentation: update CodingStyle on local variables naming in macros&apos;)Signed-off-by: Baruch Siach &lt;baruch@tkos.co.il&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Sun, 19 Apr 2015 03:35:01 +0000</pubDate>
        <dc:creator>Baruch Siach &lt;baruch@tkos.co.il&gt;</dc:creator>
    </item>
<item>
        <title>f2027543 - documentation: update CodingStyle on local variables naming in macros</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#f2027543</link>
        <description>documentation: update CodingStyle on local variables naming in macrosDescribe proper naming convention for local variables in macrosresembling functions.Signed-off-by: Bartosz Golaszewski &lt;bgolaszewski@baylibre.com&gt;Cc: Guenter Roeck &lt;linux@roeck-us.net&gt;Cc: Steven Rostedt &lt;rostedt@goodmis.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Thu, 16 Apr 2015 19:43:31 +0000</pubDate>
        <dc:creator>Bartosz Golaszewski &lt;bgolaszewski@baylibre.com&gt;</dc:creator>
    </item>
<item>
        <title>09677e0f - Documentation/CodingStyle: improve text layout</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#09677e0f</link>
        <description>Documentation/CodingStyle: improve text layoutTry to make coding style documentation look a bit more readable andconsistent with the following: - indent every code example in C to first tab-stop; - surround every code example with empty lines, both top and bottom; - remove empty lines where text looked way too spare; - do not indent examples in elisp and kconfig; - do not do any non-whitespace changes.Signed-off-by: Pavel Kretov &lt;firegurafiku@gmail.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 16 Feb 2015 17:26:18 +0000</pubDate>
        <dc:creator>Pavel Kretov &lt;firegurafiku@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>696156f0 - Documentation/CodingStyle: fix tab-spaces mixture</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#696156f0</link>
        <description>Documentation/CodingStyle: fix tab-spaces mixtureCoding style description has a irregular mixture of tabs and spaces in twoplaces which is bad by any means and can possibly hurt somebody&apos;s senseof beauty.Signed-off-by: Pavel Kretov &lt;firegurafiku@gmail.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 16 Feb 2015 17:26:17 +0000</pubDate>
        <dc:creator>Pavel Kretov &lt;firegurafiku@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>039d19a1 - CodingStyle: enable emacs display of trailing whitespace</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#039d19a1</link>
        <description>CodingStyle: enable emacs display of trailing whitespaceSuggest to developers who use emacs that they turn on theinstantaneous trailing-whitespace warning feature.Signed-off-by: Alison Chaiken &lt;alison_chaiken@mentor.com&gt;[jc: untabified to match its surroundings]Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Mon, 26 Jan 2015 03:26:01 +0000</pubDate>
        <dc:creator>Alison Chaiken &lt;alison_chaiken@mentor.com&gt;</dc:creator>
    </item>
<item>
        <title>ea040360 - CodingStyle: add some more error handling guidelines</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#ea040360</link>
        <description>CodingStyle: add some more error handling guidelinesI added a paragraph on choosing label names, and updated the examplecode to use a better label name.  I also cleaned up the example code tomore modern style by moving the allocation out of the initializer andchanging the NULL check.Perhaps the most common type of error handling bug in the kernel is &quot;oneerr bugs&quot;.  CodingStyle already says that we should &quot;avoid nesting&quot; byusing error labels and one err style error handling tends to havemultiple indent levels, so this was already bad style.  But I&apos;ve added anew paragraph explaining how to avoid one err bugs by using multipleerror 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;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Tue, 02 Dec 2014 08:59:50 +0000</pubDate>
        <dc:creator>Dan Carpenter &lt;dan.carpenter@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>21228a18 - CodingStyle: Add a chapter on conditional compilation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/CodingStyle#21228a18</link>
        <description>CodingStyle: Add a chapter on conditional compilationDocument several common practices and conventions regarding conditionalcompilation, most notably the preference for ifdefs in headers ratherthan .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;

            List of files:
            /linux-6.15/Documentation/CodingStyle</description>
        <pubDate>Wed, 29 Oct 2014 18:15:17 +0000</pubDate>
        <dc:creator>Josh Triplett &lt;josh@joshtriplett.org&gt;</dc:creator>
    </item>
</channel>
</rss>
