From: Paolo Abeni <pabeni@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Networking <netdev@vger.kernel.org>,
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 the net-next tree
Date: Mon, 11 Aug 2025 11:53:38 +0200 [thread overview]
Message-ID: <beada520-564a-481e-9f9d-91cd106aaee3@redhat.com> (raw)
In-Reply-To: <20250801144222.719c6568@canb.auug.org.au>
Hi,
On 8/1/25 6:42 AM, Stephen Rothwell wrote:
> On Fri, 11 Jul 2025 18:31:29 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the net-next tree, today's linux-next build (htmldocs)
>> produced these warnings:
>>
>> include/linux/virtio.h:172: warning: Excess struct member 'features' description in 'virtio_device'
>> include/linux/virtio.h:172: warning: Excess struct member 'features_array' description in 'virtio_device'
>>
>> Introduced by commit
>>
>> e7d4c1c5a546 ("virtio: introduce extended features")
>
> I am still seeing those warnings. That commit is now in Linus' tree.
I'm sorry for the latency, I was off-the-grid in the past weeks.
I observed that warnings in an earlier revision of the relevant patch,
but I thought the previous commit:
eade9f57ca72 ("scripts/kernel_doc.py: properly handle
VIRTIO_DECLARE_FEATURES")
addressed it. At least I can't see the warnings locally while running:
make V=1 C=1 htmldocs
Perhaps it's sphinx version dependent? I'm using sphinx-build 7.3.7
Could you please share the exact command line and tools version used?
Thanks,
Paolo
next prev parent reply other threads:[~2025-08-11 9:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 8:31 linux-next: build warnings after merge of the net-next tree Stephen Rothwell
2025-08-01 4:42 ` Stephen Rothwell
2025-08-11 9:53 ` Paolo Abeni [this message]
2025-08-12 4:36 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-11-04 5:30 Stephen Rothwell
2023-12-04 4:47 Stephen Rothwell
2023-09-18 3:15 Stephen Rothwell
2023-09-18 7:43 ` Bagas Sanjaya
2023-06-26 6:29 Stephen Rothwell
2023-09-05 22:55 ` Stephen Rothwell
2023-09-05 23:44 ` Jakub Kicinski
2023-06-13 6:31 Stephen Rothwell
2023-06-20 16:15 ` Jakub Kicinski
2023-06-20 23:12 ` Saeed Mahameed
2022-11-14 7:31 Stephen Rothwell
2022-11-14 8:00 ` Akira Yokosawa
2021-06-15 11:23 Stephen Rothwell
2021-06-15 11:12 Stephen Rothwell
2021-03-18 6:22 Stephen Rothwell
2021-02-18 20:52 Stephen Rothwell
2021-02-19 8:44 ` Stephen Rothwell
2021-02-19 14:57 ` Kalle Valo
2020-12-14 9:10 Stephen Rothwell
2020-12-21 1:28 ` Stephen Rothwell
2021-01-05 6:19 ` Stephen Rothwell
2019-11-05 1:45 Stephen Rothwell
2017-03-20 6:07 Stephen Rothwell
2017-01-18 0:37 Stephen Rothwell
2016-11-22 1:22 Stephen Rothwell
2016-11-22 1:28 ` Florian Fainelli
2016-11-22 8:23 ` Thomas Petazzoni
2015-06-20 13:12 Stephen Rothwell
2015-06-20 17:40 ` Florian Westphal
2015-06-20 18:31 ` Pablo Neira Ayuso
2015-05-14 7:12 Stephen Rothwell
2015-05-14 14:47 ` Willem de Bruijn
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=beada520-564a-481e-9f9d-91cd106aaee3@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).