All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [PATCH 4/5] doc: correct typos in switch representation guide
Date: Fri, 16 Jan 2026 13:29:35 -0800	[thread overview]
Message-ID: <20260116213100.110419-5-stephen@networkplumber.org> (raw)
In-Reply-To: <20260116213100.110419-1-stephen@networkplumber.org>

Two typos corrected:
- "according on" to "according to"
- "physical of virtual" to "physical or virtual"

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/prog_guide/ethdev/switch_representation.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/prog_guide/ethdev/switch_representation.rst b/doc/guides/prog_guide/ethdev/switch_representation.rst
index 2ef2772afb..0bc88bda8f 100644
--- a/doc/guides/prog_guide/ethdev/switch_representation.rst
+++ b/doc/guides/prog_guide/ethdev/switch_representation.rst
@@ -19,7 +19,7 @@ managed by the host system and fully transparent to users and applications.
 
 On the other hand, applications typically found on hypervisors that process
 layer 2 (L2) traffic (such as OVS) need to steer traffic themselves
-according on their own criteria.
+according to their own criteria.
 
 Without a standard software interface to manage traffic steering rules
 between VFs, SFs, PFs and the various physical ports of a given device,
@@ -84,7 +84,7 @@ thought as a software "patch panel" front-end for applications.
 - Among other things, they can be used to assign MAC addresses to the
   resource they represent.
 
-- Applications can tell port representors apart from other physical of virtual
+- Applications can tell port representors apart from other physical or virtual
   port by checking the dev_flags field within their device information
   structure for the RTE_ETH_DEV_REPRESENTOR bit-field.
 
-- 
2.51.0


  parent reply	other threads:[~2026-01-16 21:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 21:29 [PATCH 0/5] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-16 21:29 ` [PATCH 1/5] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 2/5] doc: correct grammar in rte_flow guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 3/5] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-16 21:29 ` Stephen Hemminger [this message]
2026-01-16 21:29 ` [PATCH 5/5] doc: correct typos in traffic management guide Stephen Hemminger
2026-01-28 19:45 ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 1/8] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 2/8] doc: correct grammar in flow guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 3/8] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 4/8] doc: correct typos in switch representation guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 5/8] doc: correct typos in traffic management guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 6/8] doc: correct grammar and improve clarity in ethdev guide Stephen Hemminger
2026-03-25 11:41     ` Thomas Monjalon
2026-01-28 19:46   ` [PATCH v2 7/8] doc: correct alphabetical ordering in ethdev toctree Stephen Hemminger
2026-03-25 11:45     ` Thomas Monjalon
2026-01-28 19:46   ` [PATCH v2 8/8] doc: correct grammar and improve clarity in MTR guide Stephen Hemminger
2026-02-05 21:29   ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections Stephen Hemminger

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=20260116213100.110419-5-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --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 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.