aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/documentation-file-ref-check
diff options
context:
space:
mode:
authorPeter Maydell <[email protected]>2020-04-14 14:37:43 +0000
committerJonathan Corbet <[email protected]>2020-04-15 20:58:12 +0000
commite8f4ba833166d4f589ab80630709e807a09f0b43 (patch)
tree574f3d82f8b52fd376d57adba6bdd97992454eed /scripts/documentation-file-ref-check
parentdocs: admin-guide: merge sections for the kernel.modprobe sysctl (diff)
downloadkernel-e8f4ba833166d4f589ab80630709e807a09f0b43.tar.gz
kernel-e8f4ba833166d4f589ab80630709e807a09f0b43.zip
scripts/kernel-doc: Add missing close-paren in c:function directives
When kernel-doc generates a 'c:function' directive for a function one of whose arguments is a function pointer, it fails to print the close-paren after the argument list of the function pointer argument. For instance: long work_on_cpu(int cpu, long (*fn) (void *, void * arg) in driver-api/basics.html is missing a ')' separating the "void *" of the 'fn' arguments from the ", void * arg" which is an argument to work_on_cpu(). Add the missing close-paren, so that we render the prototype correctly: long work_on_cpu(int cpu, long (*fn)(void *), void * arg) (Note that Sphinx stops rendering a space between the '(fn*)' and the '(void *)' once it gets something that's syntactically valid.) Signed-off-by: Peter Maydell <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jonathan Corbet <[email protected]>
Diffstat (limited to 'scripts/documentation-file-ref-check')
0 files changed, 0 insertions, 0 deletions