linux-kernel - Re: linux-next: build warnings after merge of Linus' 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87zf8psxz4.fsf@trenco.lwn.net>
Date: Thu, 13 Nov 2025 09:23:27 -0700
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Stephen Rothwell
 <sfr@...b.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>, Jason Wang
 <jasowang@...hat.com>, "Michael S.
 Tsirkin" <mst@...hat.com>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of Linus' tree

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

> Em Thu, 13 Nov 2025 12:55:37 +1100
> Stephen Rothwell <sfr@...b.auug.org.au> escreveu:
>
>> Hi all,
>> 
>> Today's linux-next build (htmldocs) produced these warnings:
>> 
>> WARNING: /home/sfr/kernels/next/next/include/linux/virtio_config.h:174 duplicate section name 'Return'
>> WARNING: /home/sfr/kernels/next/next/include/linux/virtio_config.h:184 duplicate section name 'Return'
>> WARNING: /home/sfr/kernels/next/next/include/linux/virtio_config.h:190 duplicate section name 'Return'
>> 
>> Introduced by commit
>> 
>>   bee8c7c24b73 ("virtio: introduce map ops in virtio core")
>> 
>> but is probably a bug in our scripts as those lines above have "Returns:"
>> in them, not "Return:".
>
> It is not a mistake. What happens is that, when kernel-doc detects
> something like:
>
> 	/**
> ...
> 	 * return: something
> ...
> 	 *    returns: else
> ...
> 	 */
>
> we have a duplicated section.

This seems like something we should be able to fix...will try to find
some time to look into it...

jon