From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Suraj Jitindar Singh <sjitindarsingh@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Alexander Graf <agraf@suse.de>, Andrew Jones <drjones@redhat.com>,
Christoffer Dall <cdall@linaro.org>,
kvm@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/4] Documentation: KVM: multiple editing corrections
Date: Fri, 16 Jun 2023 08:24:42 -0600 [thread overview]
Message-ID: <875y7nzdqt.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230612030810.23376-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Fix various issues in KVM documentation files (grammar, spelling,
> punctuation, file path, wording, hyphenation, and the location of
> module parameters).
>
>
> [PATCH 1/4] Documentation: KVM: make corrections to halt-polling.rst
> [PATCH 2/4] Documentation: KVM: make corrections to locking.rst
> [PATCH 3/4] Documentation: KVM: make corrections to ppc-pv.rst
> [PATCH 4/4] Documentation: KVM: make corrections to vcpu-requests.rst
>
> Documentation/virt/kvm/halt-polling.rst | 10 +++++-----
> Documentation/virt/kvm/locking.rst | 18 +++++++++---------
> Documentation/virt/kvm/ppc-pv.rst | 8 ++++----
> Documentation/virt/kvm/vcpu-requests.rst | 6 +++---
> 4 files changed, 21 insertions(+), 21 deletions(-)
I've applied the set, thanks.
jon
prev parent reply other threads:[~2023-06-16 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 3:08 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 ` [PATCH 4/4] Documentation: KVM: make corrections to vcpu-requests.rst Randy Dunlap
2023-06-16 14: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=875y7nzdqt.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=agraf@suse.de \
--cc=cdall@linaro.org \
--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=rdunlap@infradead.org \
--cc=seanjc@google.com \
--cc=sjitindarsingh@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 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®