From: Luiz Capitulino <lcapitulino@redhat.com>
To: rusty@rustcorp.com.au
Cc: kvm@vger.kernel.org
Subject: PATCH] virtio-spec: small English/punctuation corrections
Date: Fri, 31 May 2013 12:13:02 -0400 [thread overview]
Message-ID: <20130531121302.2d56dbe9@redhat.com> (raw)
1. s/These are devices are/These devices are
2. s/Thefirst/The first
3. s/, Guest should/. Guest should
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
---
virtio-spec.lyx | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/virtio-spec.lyx b/virtio-spec.lyx
index 6e188d0..7e4ce71 100644
--- a/virtio-spec.lyx
+++ b/virtio-spec.lyx
@@ -116,7 +116,7 @@ description "Peripheral Component Interconnect; a common device bus. See\\\\htt
\end_inset
devices.
- These are devices are found in
+ These devices are found in
\emph on
virtual
\emph default
@@ -1558,7 +1558,7 @@ name "sub:Feature-Bits"
\end_layout
\begin_layout Standard
-Thefirst configuration field indicates the features that the device supports.
+The first configuration field indicates the features that the device supports.
The bits are allocated as follows:
\end_layout
@@ -2919,7 +2919,7 @@ For each ring, guest should then disable interrupts by writing VRING_AVAIL_F_NO_
INTERRUPT flag in avail structure, if required.
It can then process used ring entries finally enabling interrupts by clearing
the VRING_AVAIL_F_NO_INTERRUPT flag or updating the EVENT_IDX field in
- the available structure, Guest should then execute a memory barrier, and
+ the available structure. Guest should then execute a memory barrier, and
then recheck the ring empty condition.
This is necessary to handle the case where, after the last check and before
enabling interrupts, an interrupt has been suppressed by the device:
--
1.8.1.4
next reply other threads:[~2013-05-31 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 16:13 Luiz Capitulino [this message]
2013-06-03 1:27 ` PATCH] virtio-spec: small English/punctuation corrections Rusty Russell
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=20130531121302.2d56dbe9@redhat.com \
--to=lcapitulino@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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