DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ray Kinsella <mdr@ashroe.eu>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, john.mcnamara@intel.com,
	aaron.conole@redhat.com, mdr@ashroe.eu
Subject: [dpdk-dev] [PATCH v2] doc: fix CI typo warnings
Date: Tue, 10 Aug 2021 15:34:20 +0100	[thread overview]
Message-ID: <20210810143420.990875-1-mdr@ashroe.eu> (raw)
In-Reply-To: <20210809130601.930651-1-mdr@ashroe.eu>

Fix documentation typos that are generating spurious CI warnings.

Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
---
v2:
  * Fix some additional typos pointed out by Aaron Conole

 doc/guides/rel_notes/deprecation.rst         | 4 ++--
 doc/guides/sample_app_ug/ioat.rst            | 2 +-
 doc/guides/sample_app_ug/vmdq_forwarding.rst | 2 +-
 examples/ioat/ioatfwd.c                      | 2 +-
 examples/vmdq/main.c                         | 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 76a4abfd6b..65023e39d8 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -208,7 +208,7 @@ Deprecation Notices
 
 * cryptodev: The structure ``rte_crypto_sym_vec`` would be updated to add
   ``dest_sgl`` to support out of place processing.
-  This field will be null for inplace processing.
+  This field will be null for in place processing.
   This change is targeted for DPDK 21.11.
 
 * cryptodev: The structure ``rte_crypto_vec`` would be updated to add
@@ -233,7 +233,7 @@ Deprecation Notices
 * security: The IPsec configuration structure
   ``struct rte_security_ipsec_xform`` will be updated with new members to allow
   SA lifetime configuration. A new structure would be introduced to replace the
-  current member, ``esn_soft_limit``.
+  current member ``esn_soft_limit``.
 
 * security: The structure ``rte_security_ipsec_xform`` will be extended with
   multiple fields: source and destination port of UDP encapsulation,
diff --git a/doc/guides/sample_app_ug/ioat.rst b/doc/guides/sample_app_ug/ioat.rst
index ee0a627b06..b364be3b5d 100644
--- a/doc/guides/sample_app_ug/ioat.rst
+++ b/doc/guides/sample_app_ug/ioat.rst
@@ -236,7 +236,7 @@ function in order to start processing for each lcore:
 .. literalinclude:: ../../../examples/ioat/ioatfwd.c
     :language: c
     :start-after: Start processing for each lcore. 8<
-    :end-before: >8 End of starting to processfor each lcore.
+    :end-before: >8 End of starting to process for each lcore.
     :dedent: 0
 
 The function launches Rx/Tx processing functions on configured lcores
diff --git a/doc/guides/sample_app_ug/vmdq_forwarding.rst b/doc/guides/sample_app_ug/vmdq_forwarding.rst
index ae1b5660df..ed28525a15 100644
--- a/doc/guides/sample_app_ug/vmdq_forwarding.rst
+++ b/doc/guides/sample_app_ug/vmdq_forwarding.rst
@@ -103,7 +103,7 @@ the MAC of VMDq pool 2 on port 1 is 52:54:00:12:01:02.
 
 .. literalinclude:: ../../../examples/vmdq/main.c
     :language: c
-    :start-after: Building correct configruration for vdmq. 8<
+    :start-after: Building correct configuration for vdmq. 8<
     :end-before: >8 End of get_eth_conf.
 
 Once the network port has been initialized using the correct VMDq values,
diff --git a/examples/ioat/ioatfwd.c b/examples/ioat/ioatfwd.c
index 0c413180f8..c57a8b82f0 100644
--- a/examples/ioat/ioatfwd.c
+++ b/examples/ioat/ioatfwd.c
@@ -564,7 +564,7 @@ static void start_forwarding_cores(void)
 			lcore_id);
 	}
 }
-/* >8 End of starting to processfor each lcore. */
+/* >8 End of starting to process for each lcore. */
 
 /* Display usage */
 static void
diff --git a/examples/vmdq/main.c b/examples/vmdq/main.c
index d3bc19f78e..843cf0bf1e 100644
--- a/examples/vmdq/main.c
+++ b/examples/vmdq/main.c
@@ -136,7 +136,7 @@ static struct rte_ether_addr vmdq_ports_eth_addr[RTE_MAX_ETHPORTS];
  * valid pool number
  */
 
- /* Building correct configruration for vdmq. 8< */
+ /* Building correct configuration for vdmq. 8< */
 static inline int
 get_eth_conf(struct rte_eth_conf *eth_conf, uint32_t num_pools)
 {
-- 
2.26.2


  parent reply	other threads:[~2021-08-10 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 13:06 [dpdk-dev] [PATCH v1] " Ray Kinsella
2021-08-09 14:43 ` Aaron Conole
2021-08-10 13:59   ` Kinsella, Ray
2021-08-10 14:34 ` Ray Kinsella [this message]
2021-08-23 15:18   ` [dpdk-dev] [PATCH v2] " Aaron Conole
2021-08-31 15:09     ` Kinsella, Ray
2021-10-28 13:50   ` Walsh, Conor
2021-11-26 13:18   ` David Marchand
2021-11-26 13:34     ` David Marchand
2021-11-26 13:37       ` Kinsella, Ray
2021-11-26 13:44         ` David Marchand

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=20210810143420.990875-1-mdr@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=aaron.conole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.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;
as well as URLs for NNTP newsgroup(s).