DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH 4/5] doc/guides: fix grammar
Date: Wed, 22 May 2019 11:44:48 +0200	[thread overview]
Message-ID: <47e0df535644ce4d6627a0cf4a52dcd8cf11ef97.1558517518.git.thierry.herbelot@6wind.com> (raw)
In-Reply-To: <eedf1632bb8ac8d15524bf42aed23095566a055e.1558517518.git.thierry.herbelot@6wind.com>
In-Reply-To: <eedf1632bb8ac8d15524bf42aed23095566a055e.1558517518.git.thierry.herbelot@6wind.com>

A copy'n'paste typo was present in three guides.

Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
---
 doc/guides/prog_guide/bbdev.rst         | 2 +-
 doc/guides/prog_guide/compressdev.rst   | 2 +-
 doc/guides/prog_guide/cryptodev_lib.rst | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index dfa0ef67d0c8..12e948a20e3d 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -284,7 +284,7 @@ baseband operations is usually completed during the enqueue call to the bbdev
 device. The dequeue burst API will retrieve any processed operations available
 from the queue on the bbdev device, from physical devices this is usually
 directly from the device's processed queue, and for virtual device's from a
-``rte_ring`` where processed operations are place after being processed on the
+``rte_ring`` where processed operations are placed after being processed on the
 enqueue call.
 
 
diff --git a/doc/guides/prog_guide/compressdev.rst b/doc/guides/prog_guide/compressdev.rst
index a06c835a03c7..07332d0048f9 100644
--- a/doc/guides/prog_guide/compressdev.rst
+++ b/doc/guides/prog_guide/compressdev.rst
@@ -568,7 +568,7 @@ operations is usually completed during the enqueue call to the compression
 device. The dequeue burst API will retrieve any processed operations available
 from the queue pair on the compression device, from physical devices this is usually
 directly from the devices processed queue, and for virtual device's from a
-``rte_ring`` where processed operations are place after being processed on the
+``rte_ring`` where processed operations are placed after being processed on the
 enqueue call.
 
 A burst in DPDK compression can be a combination of stateless and stateful operations with a condition
diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index 9bbf207646e8..2839244c50bb 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -304,7 +304,7 @@ Crypto operations is usually completed during the enqueue call to the Crypto
 device. The dequeue burst API will retrieve any processed operations available
 from the queue pair on the Crypto device, from physical devices this is usually
 directly from the devices processed queue, and for virtual device's from a
-``rte_ring`` where processed operations are place after being processed on the
+``rte_ring`` where processed operations are placed after being processed on the
 enqueue call.
 
 
-- 
2.11.0


  parent reply	other threads:[~2019-05-22  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  9:44 [dpdk-dev] [PATCH 1/5] doc/guides/cryptodevs: cleanup for armv8 and openssl PMDs Thierry Herbelot
2019-05-22  9:44 ` [dpdk-dev] [PATCH 2/5] crypto/mvsam: fix typo Thierry Herbelot
2019-05-27 13:53   ` Tomasz Duszynski
2019-05-22  9:44 ` [dpdk-dev] [PATCH 3/5] doc/prog_guides: fix triplicated typo Thierry Herbelot
2019-05-22 11:25   ` Trahe, Fiona
2019-05-22  9:44 ` Thierry Herbelot [this message]
2019-05-22  9:58   ` [dpdk-dev] [PATCH 4/5] doc/guides: fix grammar Rami Rosen
2019-05-22 11:24   ` Trahe, Fiona
2019-05-22  9:44 ` [dpdk-dev] [PATCH 5/5] drivers/{bus,crypto}: fix typo Thierry Herbelot
2019-06-18 12:56 ` [dpdk-dev] [PATCH 1/5] doc/guides/cryptodevs: cleanup for armv8 and openssl PMDs Akhil Goyal
2019-06-19 14:53 ` Akhil Goyal

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=47e0df535644ce4d6627a0cf4a52dcd8cf11ef97.1558517518.git.thierry.herbelot@6wind.com \
    --to=thierry.herbelot@6wind.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).