All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Wang Yong <yongw.kernel@gmail.com>,
	pbonzini@redhat.com, kchamart@redhat.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, Wang Yong <yongw.kernel@gmail.com>
Subject: Re: [PATCH] Documentation: KVM: fix typos in running-nested-guests.rst
Date: Thu, 26 Jan 2023 11:24:14 -0700	[thread overview]
Message-ID: <87edrh9msx.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230110150046.549755-1-yongw.kernel@gmail.com>

Wang Yong <yongw.kernel@gmail.com> writes:

> change "gues" to "guest" and remove redundant ")".
>
> Signed-off-by: Wang Yong <yongw.kernel@gmail.com>
> ---
>  Documentation/virt/kvm/x86/running-nested-guests.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/virt/kvm/x86/running-nested-guests.rst b/Documentation/virt/kvm/x86/running-nested-guests.rst
> index a27e6768d900..71136fe1723b 100644
> --- a/Documentation/virt/kvm/x86/running-nested-guests.rst
> +++ b/Documentation/virt/kvm/x86/running-nested-guests.rst
> @@ -150,7 +150,7 @@ able to start an L1 guest with::
>      $ qemu-kvm -cpu host [...]
>  
>  The above will pass through the host CPU's capabilities as-is to the
> -gues); or for better live migration compatibility, use a named CPU
> +guest, or for better live migration compatibility, use a named CPU
>  model supported by QEMU. e.g.::

Applied, thanks.

jon

      parent reply	other threads:[~2023-01-26 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 15:00 [PATCH] Documentation: KVM: fix typos in running-nested-guests.rst Wang Yong
2023-01-10 15:25 ` Kashyap Chamarthy
2023-01-26 18:24 ` Jonathan Corbet [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=87edrh9msx.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=kchamart@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=yongw.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.