Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Daniel Marcovitch <danielm@mellanox.com>
To: mst@redhat.com, virtio-dev@lists.oasis-open.org
Cc: Daniel Marcovitch <danielm@mellanox.com>
Subject: [virtio-dev] [PATCH 1/2] packed-ring/split-ring/content: fixed misc typos
Date: Tue, 30 Oct 2018 11:28:31 +0200	[thread overview]
Message-ID: <1540891712-10001-2-git-send-email-danielm@mellanox.com> (raw)
In-Reply-To: <1540891712-10001-1-git-send-email-danielm@mellanox.com>

---
 content.tex     | 2 +-
 packed-ring.tex | 2 +-
 split-ring.tex  | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/content.tex b/content.tex
index c346183..fb168a0 100644
--- a/content.tex
+++ b/content.tex
@@ -346,7 +346,7 @@ The driver MUST follow this sequence to initialize a device:
 \begin{enumerate}
 \item Reset the device.
 
-\item Set the ACKNOWLEDGE status bit: the guest OS has notice the device.
+\item Set the ACKNOWLEDGE status bit: the guest OS has noticed the device.
 
 \item Set the DRIVER status bit: the guest OS knows how to drive the device.
 
diff --git a/packed-ring.tex b/packed-ring.tex
index ebbad95..f24f49b 100644
--- a/packed-ring.tex
+++ b/packed-ring.tex
@@ -186,7 +186,7 @@ described completely by a single descriptor.
 While unusual (most implementations either create all lists
 solely using non-indirect descriptors, or always use a single
 indirect element), if both features have been negotiated, mixing
-direct and direct descriptors in a ring is valid, as long as each
+indirect and non-indirect descriptors in a ring is valid, as long as each
 list only contains descriptors of a given type.
 
 Scatter/gather lists only apply to available descriptors. A
diff --git a/split-ring.tex b/split-ring.tex
index be0cd2f..7b75b1a 100644
--- a/split-ring.tex
+++ b/split-ring.tex
@@ -220,7 +220,7 @@ read a device-writable buffer (it MAY do so for debugging or diagnostic
 purposes).
 
 \drivernormative{\subsubsection}{The Virtqueue Descriptor Table}{Basic Facilities of a Virtio Device / Virtqueues / The Virtqueue Descriptor Table}
-Drivers MUST NOT add a descriptor chain over than $2^{32}$ bytes long in total;
+Drivers MUST NOT add a descriptor chain over $2^{32}$ bytes long in total;
 this implies that loops in the descriptor chain are forbidden!
 
 If VIRTIO_F_IN_ORDER has been negotiated, and when making a
@@ -560,7 +560,7 @@ The driver offers buffers to one of the device's virtqueues as follows:
 \item Steps \ref{itm:Basic Facilities of a Virtio Device / Virtqueues / Supplying Buffers to The Device / Place Buffers} and \ref{itm:Basic Facilities of a Virtio Device / Virtqueues / Supplying Buffers to The Device / Place Index} MAY be performed repeatedly if batching
   is possible.
 
-\item The driver performs suitable a memory barrier to ensure the device sees
+\item The driver performs a suitable memory barrier to ensure the device sees
   the updated descriptor table and available ring before the next
   step.
 
-- 
1.8.3.1


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2018-10-30  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30  9:28 [virtio-dev] [PATCH 0/2] Typos, grammar and cosmetic fixes Daniel Marcovitch
2018-10-30  9:28 ` Daniel Marcovitch [this message]
2018-10-30 10:59   ` [virtio-dev] [PATCH 1/2] packed-ring/split-ring/content: fixed misc typos Cornelia Huck
2018-10-30 11:07   ` Stefan Hajnoczi
2018-10-30  9:28 ` [virtio-dev] [PATCH 2/2] queue_size: renamed "hypervisor" to "device" Daniel Marcovitch
2018-10-30 11:01   ` Cornelia Huck
2018-10-30 11:06   ` Stefan Hajnoczi

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=1540891712-10001-2-git-send-email-danielm@mellanox.com \
    --to=danielm@mellanox.com \
    --cc=mst@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    /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