From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Wang, Wei W" <wei.w.wang@intel.com>, KVM <kvm@vger.kernel.org>,
"Zeng, Guang" <guang.zeng@intel.com>,
"Liu, Jing2" <jing2.liu@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Zhong, Yang" <yang.zhong@intel.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 kvm tree
Date: Thu, 20 Jan 2022 14:36:19 +1100 [thread overview]
Message-ID: <20220120143619.4803cb36@canb.auug.org.au> (raw)
In-Reply-To: <507a652f97de4e0fb26d604084ef6f25@intel.com>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Hi all,
On Tue, 11 Jan 2022 02:55:56 +0000 "Wang, Wei W" <wei.w.wang@intel.com> wrote:
>
> On Monday, January 10, 2022 4:59 PM, Stephen Rothwell wrote:
> > After merging the kvm tree, today's linux-next build (htmldocs) produced this
> > warning:
> >
> > Documentation/virt/kvm/api.rst:5549: WARNING: Title underline too short.
> >
> > 4.42 KVM_GET_XSAVE2
> > ------------------
>
> Should add one more "_" above.
> 4.42 KVM_GET_XSAVE2
> -------------------
> +-------------------
>
> Paolo, do you want us to send another patch to add it or you can just add it?
I am still seeing this warning.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-20 3:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 8:58 linux-next: build warning after merge of the kvm tree Stephen Rothwell
2022-01-11 2:55 ` Wang, Wei W
2022-01-20 3:36 ` Stephen Rothwell [this message]
2022-01-20 5:52 ` Wang, Wei W
-- 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
2021-04-22 8:53 Stephen Rothwell
2021-02-09 9:59 Stephen Rothwell
2021-02-09 10:01 ` Paolo Bonzini
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=20220120143619.4803cb36@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=guang.zeng@intel.com \
--cc=jing2.liu@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wei.w.wang@intel.com \
--cc=yang.zhong@intel.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 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).