From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
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, 21 Mar 2023 22:24:22 -0400 [thread overview]
Message-ID: <20230321222404-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230322123231.2c5cbce5@canb.auug.org.au>
On Wed, Mar 22, 2023 at 12:32:31PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the vhost tree, today's linux-next build (htmldocs)
> produced this warning:
>
> drivers/virtio/virtio_ring.c:2346: warning: Excess function parameter 'vq' description in 'virtqueue_dma_dev'
>
> Introduced by commit
>
> 9225f75b9b80 ("virtio_ring: introduce virtqueue_dma_dev()")
>
> --
> Cheers,
> Stephen Rothwell
Fixed up, thanks, no need to repost the patch.
--
MST
next prev parent reply other threads:[~2023-03-22 2:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 1:32 linux-next: build warning after merge of the vhost tree Stephen Rothwell
2023-03-22 2:24 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-15 7:10 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
2024-07-16 11:29 ` Jiri Pirko
2024-02-23 4:10 Stephen Rothwell
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=20230321222404-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xuanzhuo@linux.alibaba.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.