From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Andrew Jones <drjones@redhat.com>,
Christoffer Dall <cdall@linaro.org>,
kvm@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [PATCH 4/4] Documentation: KVM: make corrections to vcpu-requests.rst
Date: Sun, 11 Jun 2023 20:08:10 -0700 [thread overview]
Message-ID: <20230612030810.23376-5-rdunlap@infradead.org> (raw)
In-Reply-To: <20230612030810.23376-1-rdunlap@infradead.org>
Make corrections to punctuation and grammar.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>
Cc: Andrew Jones <drjones@redhat.com>
Cc: Christoffer Dall <cdall@linaro.org>
Cc: kvm@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
Documentation/virt/kvm/vcpu-requests.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -- a/Documentation/virt/kvm/vcpu-requests.rst b/Documentation/virt/kvm/vcpu-requests.rst
--- a/Documentation/virt/kvm/vcpu-requests.rst
+++ b/Documentation/virt/kvm/vcpu-requests.rst
@@ -101,7 +101,7 @@ also be used, e.g. ::
However, VCPU request users should refrain from doing so, as it would
break the abstraction. The first 8 bits are reserved for architecture
-independent requests, all additional bits are available for architecture
+independent requests; all additional bits are available for architecture
dependent requests.
Architecture Independent Requests
@@ -151,8 +151,8 @@ KVM_REQUEST_NO_WAKEUP
This flag is applied to requests that only need immediate attention
from VCPUs running in guest mode. That is, sleeping VCPUs do not need
- to be awaken for these requests. Sleeping VCPUs will handle the
- requests when they are awaken later for some other reason.
+ to be awakened for these requests. Sleeping VCPUs will handle the
+ requests when they are awakened later for some other reason.
KVM_REQUEST_WAIT
next prev parent reply other threads:[~2023-06-12 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 3:08 [PATCH 0/4] Documentation: KVM: multiple editing corrections Randy Dunlap
2023-06-12 3:08 ` [PATCH 1/4] Documentation: KVM: make corrections to halt-polling.rst Randy Dunlap
2023-06-12 3:08 ` [PATCH 2/4] Documentation: KVM: make corrections to locking.rst Randy Dunlap
2023-06-12 3:08 ` [PATCH 3/4] Documentation: KVM: make corrections to ppc-pv.rst Randy Dunlap
2023-06-12 3:08 ` Randy Dunlap [this message]
2023-06-16 14:24 ` [PATCH 0/4] Documentation: KVM: multiple editing corrections Jonathan Corbet
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=20230612030810.23376-5-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=cdall@linaro.org \
--cc=corbet@lwn.net \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®