A small fix for parse-headers.rst
cover A small fix for parse-headers.rst
Hi Jon,
This was supposed to be part of v4 of
https://lore.kernel.org/linux-doc/[email protected]/,
but it ended I didn't merge it, as I forgot to use "-a" on git commit...
Mauro Carvalho Chehab (1):
docs: parse-headers.rst: remove uneeded parenthesis
Documentation/doc-guide/parse-headers.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 1 line
2.51.1
PATCH 1/1 docs: parse-headers.rst: remove uneeded parenthesis
As pointed by Randy, the parenthesis there is not needed and it violates the document coding style.
Reported-by Randy Dunlap <[email protected]>
Signed-off-by Mauro Carvalho Chehab <[email protected]>
--- Documentation/doc-guide/parse-headers.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/doc-guide/parse-headers.rst +1 -1
@@ -89,7 +89,7 @@ defines the C namespace to be used. It is meant to allow having more comprehensive documentation, where uAPI headers will create cross-reference links to the code. -The output is written at the (``FILE_OUT``). +The output is written at the ``FILE_OUT``. The ``FILE_RULES`` may contain contain three types of statements: **ignore**, **replace** and **namespace**.
Signature · 1 line
2.51.1
Re: [PATCH 1/1] docs: parse-headers.rst: remove uneeded parenthesis
Quoted 15 lines · Mauro Carvalho Chehab
As pointed by Randy, the parenthesis there is not needed and it violates the document coding style.
Reported-by Randy Dunlap <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/doc-guide/parse-headers.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/doc-guide/parse-headers.rst +0
-0
Documentation/doc-guide/parse-headers.rst defines the C namespace to be used. · line 92
Quoted 5 lines
Documentation/doc-guide/parse-headers.rst +1
-1@@ -89,7 +89,7 @@ defines the C namespace to be used. It is meant to allow having more comprehensive documentation, where uAPI headers will create cross-reference links to the code. -The output is written at the (``FILE_OUT``). +The output is written at the ``FILE_OUT``.
Applied, thanks.
jon