public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Ricardo Cañuelo" <ricardo.canuelo@collabora.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, 20 Dec 2022 01:01:03 -0500	[thread overview]
Message-ID: <20221220010040-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221220105956.4786852d@canb.auug.org.au>

On Tue, Dec 20, 2022 at 10:59:56AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the vhost tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> include/linux/virtio_config.h:74: warning: duplicate section name 'Note'
> include/linux/virtio_config.h:94: warning: expecting prototype for virtio_config_ops(). Prototype was for vq_callback_t() instead
> 
> Revelealed by commit
> 
>   333723e8bc39 ("docs: driver-api: virtio: virtio on Linux")


Ricardo I assume you will fix this? Patch on top is ok.

> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2022-12-20  6:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 23:59 linux-next: build warning after merge of the vhost tree Stephen Rothwell
2022-12-20  6:01 ` Michael S. Tsirkin [this message]
2022-12-20  7:04   ` Ricardo Cañuelo
  -- 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
2023-03-22  1:32 Stephen Rothwell
2023-03-22  2:24 ` Michael S. Tsirkin
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=20221220010040-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ricardo.canuelo@collabora.com \
    --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