From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jason Wang <jasowang@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of Linus' tree
Date: Thu, 13 Nov 2025 03:49:27 -0500 [thread overview]
Message-ID: <20251113031422-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20251113125537.0d08e5ce@canb.auug.org.au>
On Thu, Nov 13, 2025 at 12:55:37PM +1100, Stephen Rothwell wrote:
> 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:".
>
> These have turned up now since a bug was fixed that was repressing a
> lot of warnings.
Indeed. But the rest of header says Returns ... without : so I will just
fix this one to do the same. I also fixed other issues in the comments
in this header while I was at it. Will post shortly.
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2025-11-13 8:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 1:55 linux-next: build warnings after merge of Linus' tree Stephen Rothwell
2025-11-13 8:16 ` Mauro Carvalho Chehab
2025-11-13 16:23 ` Jonathan Corbet
2025-11-13 22:01 ` Mauro Carvalho Chehab
2025-11-13 22:28 ` Randy Dunlap
2025-11-13 22:42 ` Randy Dunlap
2025-11-13 8:49 ` Michael S. Tsirkin [this message]
2025-11-13 10:32 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2025-04-07 8:59 Venkat
2025-04-07 9:47 ` Venkat Rao Bagalkote
2025-04-06 22:48 Stephen Rothwell
2023-05-08 4:49 Stephen Rothwell
2023-05-08 4:52 ` Randy Dunlap
2023-05-08 4:53 ` Randy Dunlap
2023-05-08 7:50 ` Peter Zijlstra
2021-03-29 9:04 Stephen Rothwell
2021-04-21 6:23 ` Stephen Rothwell
2021-04-21 13:06 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251113031422-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=corbet@lwn.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox