summaryrefslogtreecommitdiffstats
path: root/scripts/docproc.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* kbuild: trivial - use tabs for code indent where possibleMasahiro Yamada2014-06-101-28/+28
| | | | | Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Signed-off-by: Michal Marek <mmarek@suse.cz>
* kernel-doc: improve "no structured comments found" errorJohannes Berg2013-11-131-5/+9
| | | | | | | | | | | | | | | | | | | 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 <johannes.berg@intel.com> Cc: Rob Landley <rob@landley.net> Cc: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
* docproc: cleanup brace placementJesper Juhl2011-06-161-12/+5
| | | | | | | | | | | 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 <jj@chaosbits.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
* kbuild: move scripts/basic/docproc.c to scripts/docproc.cPeter Foley2011-05-021-0/+583
Move docproc from scripts/basic to scripts so it is only built for *doc targets instead of every time the kernel is built.