diff options
author | Peter Maydell <peter.maydell@linaro.org> | 2020-04-14 15:37:43 +0100 |
---|---|---|
committer | Jonathan Corbet <corbet@lwn.net> | 2020-04-15 14:58:12 -0600 |
commit | e8f4ba833166d4f589ab80630709e807a09f0b43 (patch) | |
tree | 574f3d82f8b52fd376d57adba6bdd97992454eed /scripts | |
parent | 52338dfb3ca11e6a99288e9e9e4019f279822ddd (diff) | |
download | linux-e8f4ba833166d4f589ab80630709e807a09f0b43.tar.gz linux-e8f4ba833166d4f589ab80630709e807a09f0b43.tar.bz2 linux-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 <peter.maydell@linaro.org>
Link: https://lore.kernel.org/r/20200414143743.32677-1-peter.maydell@linaro.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'scripts')
-rwxr-xr-x | scripts/kernel-doc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/kernel-doc b/scripts/kernel-doc index f2d73f04e71d..f746ca8fa403 100755 --- a/scripts/kernel-doc +++ b/scripts/kernel-doc @@ -853,7 +853,7 @@ sub output_function_rst(%) { if ($type =~ m/([^\(]*\(\*)\s*\)\s*\(([^\)]*)\)/) { # pointer-to-function - print $1 . $parameter . ") (" . $2; + print $1 . $parameter . ") (" . $2 . ")"; } else { print $type . " " . $parameter; } |