From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: [PATCH 2/2] Documentation: virt: kvm/s390-pv: drop doubled words
Date: Fri, 3 Jul 2020 14:29:05 -0700 [thread overview]
Message-ID: <20200703212906.30655-2-rdunlap@infradead.org> (raw)
In-Reply-To: <20200703212906.30655-1-rdunlap@infradead.org>
Drop the doubled word "the".
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org
---
Documentation/virt/kvm/s390-pv.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20200701.orig/Documentation/virt/kvm/s390-pv.rst
+++ linux-next-20200701/Documentation/virt/kvm/s390-pv.rst
@@ -78,7 +78,7 @@ Register Save Area.
Only GR values needed to emulate an instruction will be copied into this
save area and the real register numbers will be hidden.
-The Interception Parameters state description field still contains the
+The Interception Parameters state description field still contains
the bytes of the instruction text, but with pre-set register values
instead of the actual ones. I.e. each instruction always uses the same
instruction text, in order not to leak guest instruction text.
next prev parent reply other threads:[~2020-07-03 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 21:29 [PATCH 0/2] Documentation: virt: eliminate duplicated words Randy Dunlap
2020-07-03 21:29 ` Randy Dunlap [this message]
2020-07-03 21:29 ` [PATCH 1/2] Documentation: virt: kvm/api: drop doubled words Randy Dunlap
2020-07-05 20:42 ` [PATCH 0/2] Documentation: virt: eliminate duplicated words 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=20200703212906.30655-2-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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.