mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wei Wang <wei.w.wang@intel.com>, sfr@canb.auug.org.au
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: kvm: fix WARNINGs from api.rst
Date: Thu, 20 Jan 2022 18:13:38 +0100	[thread overview]
Message-ID: <39bb00be-e4e4-1eb5-de25-192d66aa2bc4@redhat.com> (raw)
In-Reply-To: <20220120045003.315177-1-wei.w.wang@intel.com>

On 1/20/22 05:50, Wei Wang wrote:
> Use the api number 134 for KVM_GET_XSAVE2, instead of 42, which has been
> used by KVM_GET_XSAVE.
> Also, fix the WARNINGs of the underlines being too short.
> 
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Wei Wang <wei.w.wang@intel.com>
> ---
>   Documentation/virt/kvm/api.rst | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index d3791a14eb9a..bb8cfddbb22d 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -5545,8 +5545,8 @@ the trailing ``'\0'``, is indicated by ``name_size`` in the header.
>   The Stats Data block contains an array of 64-bit values in the same order
>   as the descriptors in Descriptors block.
>   
> -4.42 KVM_GET_XSAVE2
> -------------------
> +4.134 KVM_GET_XSAVE2
> +--------------------
>   
>   :Capability: KVM_CAP_XSAVE2
>   :Architectures: x86
> @@ -7363,7 +7363,7 @@ trap and emulate MSRs that are outside of the scope of KVM as well as
>   limit the attack surface on KVM's MSR emulation code.
>   
>   8.28 KVM_CAP_ENFORCE_PV_FEATURE_CPUID
> ------------------------------
> +-------------------------------------
>   
>   Architectures: x86
>   

Queued, thanks.

Paolo


      parent reply	other threads:[~2022-01-20 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20  4:50 Wei Wang
2022-01-20 11:20 ` Stephen Rothwell
2022-01-20 17:13 ` Paolo Bonzini [this message]

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=39bb00be-e4e4-1eb5-de25-192d66aa2bc4@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wei.w.wang@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

Powered by JetHome