[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e76610ec-2efa-4333-1f6d-6072c1412d24@infradead.org>
Date: Mon, 6 Feb 2023 08:31:38 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Deming Wang <wangdeming@...pur.com>, pbonzini@...hat.com,
corbet@....net
Cc: kvm@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: kvm: Correct spelling
Hi,
On 2/6/23 01:11, Deming Wang wrote:
> We shuold use the replace thie.
>
> Signed-off-by: Deming Wang <wangdeming@...pur.com>
> ---
> Documentation/virt/kvm/api.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 1b1f721e3fd9..4e164d449906 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -8193,7 +8193,7 @@ the KVM_XEN_ATTR_TYPE_RUNSTATE_UPDATE_FLAG attribute in the KVM_XEN_SET_ATTR
> and KVM_XEN_GET_ATTR ioctls. This controls whether KVM will set the
> XEN_RUNSTATE_UPDATE flag in guest memory mapped vcpu_runstate_info during
> updates of the runstate information. Note that versions of KVM which support
> -the RUNSTATE feature above, but not thie RUNSTATE_UPDATE_FLAG feature, will
> +the RUNSTATE feature above, but not the RUNSTATE_UPDATE_FLAG feature, will
> always set the XEN_RUNSTATE_UPDATE flag when updating the guest structure,
> which is perhaps counterintuitive. When this flag is advertised, KVM will
> behave more correctly, not using the XEN_RUNSTATE_UPDATE flag until/unless
How about these in the same file?
api.rst:581: virutal ==> virtual
api.rst:2725: excution ==> execution
api.rst:5207: asynchonous ==> asynchronous
api.rst:5666: thats ==> that's [should just be "that"]
api.rst:7420: priveleged ==> privileged
api.rst:7838: compatibilty ==> compatibility
api.rst:8241: implmented ==> implemented
and this one:
halt-polling.rst:17: dependant ==> dependent
and there are more in the subdirectories there.
--
~Randy
Powered by blists - more mailing lists