<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git/scripts/docproc.c, branch v4.9.40</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.9.40</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.9.40'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2016-05-14T15:56:56Z</updated>
<entry>
<title>docproc: print a comment about autogeneration for rst output</title>
<updated>2016-05-14T15:56:56Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2016-05-12T13:15:44Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=0e95abf9be3108498128458ffb087209e0a1b5fa'/>
<id>urn:sha1:0e95abf9be3108498128458ffb087209e0a1b5fa</id>
<content type='text'>
Leave a hint to folks which file to edit instead.

Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docproc: add support for reStructuredText format via --rst option</title>
<updated>2016-05-14T15:56:53Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2016-05-12T13:15:43Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=064669b43baa4b74b262c49db3ce69118e2f0f2d'/>
<id>urn:sha1:064669b43baa4b74b262c49db3ce69118e2f0f2d</id>
<content type='text'>
Expect reStructuredText input and have kernel-doc produce
reStructuredText output with the new --rst option. Also add --docbook
option for completeness. If no option is given, default to
reStructuredText if the input file has ".rst" extension, DocBook
otherwise.

Directives for reStructuredText use .. ! instead of just !, to make them
reStructuredText comments.

Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docproc: abstract terminating lines at first space</title>
<updated>2016-05-14T15:56:49Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2016-05-12T13:15:42Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=1dcdad0aacb6d762b77f3e17167d131a14c0dbce'/>
<id>urn:sha1:1dcdad0aacb6d762b77f3e17167d131a14c0dbce</id>
<content type='text'>
Cleaner code. Also fixes a bug when F or P directives didn't in fact
have space.

Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docproc: abstract docproc directive detection</title>
<updated>2016-05-14T15:56:45Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2016-05-12T13:15:41Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=a48dc45e9c02ebaebc79de5b3fec8e4f59a9fe9f'/>
<id>urn:sha1:a48dc45e9c02ebaebc79de5b3fec8e4f59a9fe9f</id>
<content type='text'>
Helps follow-up work. No functional changes.

Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docproc: reduce unnecessary indentation</title>
<updated>2016-05-14T15:56:41Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2016-05-12T13:15:40Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=868fb19212ca5bdbfa765a97a4bf6d2439b89056'/>
<id>urn:sha1:868fb19212ca5bdbfa765a97a4bf6d2439b89056</id>
<content type='text'>
Improves clarity. No functional changes.

Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docproc: add variables for subcommand and filename</title>
<updated>2016-05-14T15:56:37Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2016-05-12T13:15:39Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=568fb2dec9c68bb38c2a1ad01fb3d4dd41488115'/>
<id>urn:sha1:568fb2dec9c68bb38c2a1ad01fb3d4dd41488115</id>
<content type='text'>
Improves clarity. No functional changes.

Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>kbuild: trivial - use tabs for code indent where possible</title>
<updated>2014-06-10T12:00:53Z</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.m@jp.panasonic.com</email>
</author>
<published>2014-06-10T10:08:13Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=bb66fc67192bbd406fe9c22033f1bbbf3e7ec621'/>
<id>urn:sha1:bb66fc67192bbd406fe9c22033f1bbbf3e7ec621</id>
<content type='text'>
Signed-off-by: Masahiro Yamada &lt;yamada.m@jp.panasonic.com&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>kernel-doc: improve "no structured comments found" error</title>
<updated>2013-11-13T03:09:32Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2013-11-12T23:11:12Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=e946c43a116526e3d947dc03aeb165c1effd9f8f'/>
<id>urn:sha1:e946c43a116526e3d947dc03aeb165c1effd9f8f</id>
<content type='text'>
When using '!Ffile function' in a docbook template, and the function no
longer exists, you get a "no structured comments found" error from the
kernel-doc processing script.  It's useful to know which functions it was
looking for, so print them out in this case.  Also do the same for '!Pfile
doc-section'

The same error also happens when using '!Efile' when some exported
functions aren't documented (in the same file.) There's a very large
number of such functions though, so don't print the message in this case
-- right now it would give ~850 messages.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Cc: Rob Landley &lt;rob@landley.net&gt;
Cc: Randy Dunlap &lt;rdunlap@infradead.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>docproc: cleanup brace placement</title>
<updated>2011-06-16T18:40:03Z</updated>
<author>
<name>Jesper Juhl</name>
<email>jj@chaosbits.net</email>
</author>
<published>2011-06-15T09:53:13Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=f0f3ca8d967462dafb815412b14ca3339b9817a6'/>
<id>urn:sha1:f0f3ca8d967462dafb815412b14ca3339b9817a6</id>
<content type='text'>
The placement of the opening brace "{" after 'if' statements in
scripts/docproc.c is inconsistent. Most are placed on the same line as the 'if'
statement itself as per CodingStyle, but a few are not.  This patch cleans up
the inconsistency. We save a few source lines and the file then uses the same
style throughout, which is nice.

Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>kbuild: move scripts/basic/docproc.c to scripts/docproc.c</title>
<updated>2011-05-02T20:48:03Z</updated>
<author>
<name>Peter Foley</name>
<email>pefoley2@verizon.net</email>
</author>
<published>2011-05-02T20:48:03Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=bffd2020a972a188750e5cf4b9566950dfdf25a2'/>
<id>urn:sha1:bffd2020a972a188750e5cf4b9566950dfdf25a2</id>
<content type='text'>
Move docproc from scripts/basic to scripts so it is only built for *doc
targets instead of every time the kernel is built.
</content>
</entry>
</feed>
