linux-kernel - Re: [PATCH 1/1] docs: parse-headers.rst: remove uneeded parenthesis

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87jyztsxfv.fsf@trenco.lwn.net>
Date: Thu, 13 Nov 2025 09:35:00 -0700
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Linux Doc Mailing
 List <linux-doc@...r.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Dongliang Mu
 <dzm91@...t.edu.cn>, Mauro Carvalho Chehab <mchehab@...nel.org>, Randy
 Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] docs: parse-headers.rst: remove uneeded parenthesis

Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:

> As pointed by Randy, the parenthesis there is not needed and it
> violates the document coding style.
>
> Reported-by: Randy Dunlap <rdunlap@...radead.org>
> Closes: https://lore.kernel.org/linux-doc/9d709020-03fe-467c-be7f-d5ee251bb79a@infradead.org/
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> ---
>  Documentation/doc-guide/parse-headers.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/doc-guide/parse-headers.rst b/Documentation/doc-guide/parse-headers.rst
> index 954f3285ddf6..bd34a6d00ca9 100644
> --- a/Documentation/doc-guide/parse-headers.rst
> +++ b/Documentation/doc-guide/parse-headers.rst
> @@ -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