From: "Ricardo Cañuelo" <ricardo.canuelo@collabora•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
"Michael S. Tsirkin" <mst@redhat•com>
Cc: 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: Thu, 11 Aug 2022 08:45:08 +0200 [thread overview]
Message-ID: <d74f15ba-8b76-3a76-a1f5-10855bf459b0@collabora.com> (raw)
In-Reply-To: <20220811115917.1b5c9a57@canb.auug.org.au>
Hi Stephen, Michael,
On 11/8/22 3:59, Stephen Rothwell wrote:
> Hi all,
>
> After merging the vhost tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/driver-api/index.rst:14: WARNING: toctree contains reference to nonexisting document 'driver-api/virtio/index'
>
> Introduced by commit
>
> 6355eeb59129 ("docs: driver-api: virtio: virtio on Linux")
>
The patch that ended up in the vhost tree is only a part of the
complete patch:
https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?h=linux-next&id=6355eeb59129a31aed0adb60d174df63a5630f8e
The full patch is this:
https://lore.kernel.org/linux-doc/20220810094004.1250-1-ricardo.canuelo@collabora.com/T/#t
Cheers,
Ricardo
next prev parent reply other threads:[~2022-08-11 6:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 1:59 linux-next: build warning after merge of the vhost tree Stephen Rothwell
2022-08-11 6:45 ` Ricardo Cañuelo [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
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-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=d74f15ba-8b76-3a76-a1f5-10855bf459b0@collabora.com \
--to=ricardo.canuelo@collabora$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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