From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jiri Pirko <jiri@nvidia.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Jiri Pirko <jiri@resnulli.us>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the vhost tree
Date: Tue, 16 Jul 2024 07:05:12 -0400 [thread overview]
Message-ID: <20240716070452-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <ZpYURX4IrW05U_O5@nanopsycho.orion>
On Tue, Jul 16, 2024 at 08:33:41AM +0200, Jiri Pirko wrote:
> Mon, Jul 15, 2024 at 10:50:43AM CEST, mst@redhat.com wrote:
> >On Mon, Jul 15, 2024 at 10:01:47AM +0200, Jiri Pirko wrote:
> >> Mon, Jul 15, 2024 at 09:10:41AM CEST, sfr@canb.auug.org.au wrote:
> >> >Hi all,
> >> >
> >> >After merging the vhost tree, today's linux-next build (htmldocs)
> >> >produced this warning:
> >> >
> >> >include/linux/virtio_config.h:136: warning: Excess struct member 'create_avq' description in 'virtio_config_ops'
> >> >include/linux/virtio_config.h:136: warning: Excess struct member 'destroy_avq' description in 'virtio_config_ops'
> >> >
> >> >Introduced by commit
> >> >
> >> > e6bb1118f6da ("virtio: create admin queues alongside other virtqueues")
> >>
> >> Ah, leftover, will send fix. Thx!
> >
> >Better squash it.
>
> Does it mean you take care of that in your tree?
>
> >
> >> >
> >> >--
> >> >Cheers,
> >> >Stephen Rothwell
> >>
> >
It's easier for me if you just post a new version of the patchset.
--
MST
next prev parent reply other threads:[~2024-07-16 11:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 7:10 linux-next: build warning after merge of the vhost tree Stephen Rothwell
2024-07-15 8:01 ` Jiri Pirko
2024-07-15 8:50 ` Michael S. Tsirkin
2024-07-16 6:33 ` Jiri Pirko
2024-07-16 11:05 ` Michael S. Tsirkin [this message]
2024-07-16 11:29 ` Jiri Pirko
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 4:10 Stephen Rothwell
2023-03-22 1:32 Stephen Rothwell
2023-03-22 2:24 ` Michael S. Tsirkin
2022-12-19 23:59 Stephen Rothwell
2022-12-20 6:01 ` Michael S. Tsirkin
2022-12-20 7:04 ` Ricardo Cañuelo
2022-08-11 1:59 Stephen Rothwell
2022-08-11 6:45 ` Ricardo Cañuelo
2022-03-07 4:40 Stephen Rothwell
2022-03-07 6:46 ` Xuan Zhuo
2022-03-07 9:17 ` Michael S. Tsirkin
2022-03-07 9:41 ` Xuan Zhuo
2022-03-07 10:12 ` Stephen Rothwell
2022-03-07 11:00 ` Michael S. Tsirkin
2022-03-09 6:13 ` Stephen Rothwell
2022-03-09 6:15 ` Xuan Zhuo
2022-03-09 6:30 ` Xuan Zhuo
2021-07-06 2:37 Stephen Rothwell
2020-06-09 3:25 Stephen Rothwell
2019-12-16 3:49 Stephen Rothwell
2019-11-15 4:36 Stephen Rothwell
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=20240716070452-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).