From: Paolo Bonzini <pbonzini@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, KVM <kvm@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: linux-next: build warning after merge of the kvm tree
Date: Tue, 9 Feb 2021 11:01:34 +0100 [thread overview]
Message-ID: <23ec3e79-1b6d-a116-ff52-3c5c1d0308d1@redhat.com> (raw)
In-Reply-To: <20210209205950.7be889db@canb.auug.org.au>
On 09/02/21 10:59, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kvm tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/virt/kvm/api.rst:4927: WARNING: Title underline too short.
>
> 4.130 KVM_XEN_VCPU_GET_ATTR
> --------------------------
>
> Introduced by commit
>
> e1f68169a4f8 ("KVM: Add documentation for Xen hypercall and shared_info updates")
>
Thanks, will fix.
Paolo
next prev parent reply other threads:[~2021-02-09 10:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 9:59 linux-next: build warning after merge of the kvm tree Stephen Rothwell
2021-02-09 10:01 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 3:13 Stephen Rothwell
2023-11-14 12:50 ` Paolo Bonzini
2022-12-13 4:41 Stephen Rothwell
2022-12-13 5:11 ` Sean Christopherson
2022-06-27 8:19 Stephen Rothwell
2022-06-27 9:57 ` Bagas Sanjaya
2022-08-09 6:41 ` Stephen Rothwell
2022-01-10 8:58 Stephen Rothwell
2022-01-11 2:55 ` Wang, Wei W
2022-01-20 3:36 ` Stephen Rothwell
2022-01-20 5:52 ` Wang, Wei W
2021-04-22 8:53 Stephen Rothwell
2019-11-25 3:03 Stephen Rothwell
2013-01-10 2:34 Stephen Rothwell
2013-01-10 6:56 ` Gleb Natapov
2010-07-26 5:14 Stephen Rothwell
2010-05-27 4:53 Stephen Rothwell
2010-05-27 10:19 ` Roedel, Joerg
2010-05-27 10:49 ` Stephen Rothwell
2010-05-27 12:13 ` Avi Kivity
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=23ec3e79-1b6d-a116-ff52-3c5c1d0308d1@redhat.com \
--to=pbonzini@redhat.com \
--cc=dwmw@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--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).