linux-kernel - Re: linux-next: build warning after merge of the xfs tree

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]

Date: Mon, 26 Feb 2024 11:57:27 +0100
From: Christoph Hellwig <hch@....de>
To: Akira Yokosawa <akiyks@...il.com>
Cc: hch@....de, chandanbabu@...nel.org, corbet@....net, david@...morbit.com,
	djwong@...nel.org, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, linux-xfs@...r.kernel.org,
	mchehab@...nel.org, sfr@...b.auug.org.au
Subject: Re: linux-next: build warning after merge of the xfs tree

On Sat, Feb 24, 2024 at 06:07:28PM +0900, Akira Yokosawa wrote:
> How about teaching kernel-doc unary "*" on param?

That would be great!

> 
> Substitution would look like:
> 
>    (kernel-doc)       (RST)
>    *@...am     ->  ***param**
> 
> Sphinx detects double asterisk, starts strong emphasis, waits for
> another double asterisk to appear, and stops strong emphasis.
> Hence you would get boldface "*param" in pretty printed docs.
> 
> Diff below (against docs-next) should add a rule for param_deref
> (only for RST).

I'd love to go with this instead of working around the issue:

Acked-by: Christoph Hellwig <hch@....de>