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>
Subject: [dpdk-dev] [PATCH 16/30] examples/ethtool: fix spelling errors
Date: Mon,  1 Jul 2019 11:25:22 -0700	[thread overview]
Message-ID: <20190701182536.20110-17-stephen@networkplumber.org> (raw)
In-Reply-To: <20190701182536.20110-1-stephen@networkplumber.org>

Spelling errors found by codespell.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 examples/ethtool/lib/rte_ethtool.c | 2 +-
 examples/ethtool/lib/rte_ethtool.h | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/examples/ethtool/lib/rte_ethtool.c b/examples/ethtool/lib/rte_ethtool.c
index 571c4e5aa52c..ec543055e483 100644
--- a/examples/ethtool/lib/rte_ethtool.c
+++ b/examples/ethtool/lib/rte_ethtool.c
@@ -376,7 +376,7 @@ rte_ethtool_net_set_rx_mode(uint16_t port_id)
 	rte_eth_dev_info_get(port_id, &dev_info);
 	num_vfs = dev_info.max_vfs;
 
-	/* Set VF vf_rx_mode, VF unsupport status is discard */
+	/* Set VF vf_rx_mode, VF unsupported status is discard */
 	for (vf = 0; vf < num_vfs; vf++) {
 #ifdef RTE_LIBRTE_IXGBE_PMD
 		rte_pmd_ixgbe_set_vf_rxmode(port_id, vf,
diff --git a/examples/ethtool/lib/rte_ethtool.h b/examples/ethtool/lib/rte_ethtool.h
index f17709663644..d27e0102b1ca 100644
--- a/examples/ethtool/lib/rte_ethtool.h
+++ b/examples/ethtool/lib/rte_ethtool.h
@@ -189,7 +189,7 @@ int rte_ethtool_get_module_eeprom(uint16_t port_id,
 
 /**
  * Retrieve the Ethernet device pause frame configuration according to
- * parameter attributes desribed by ethtool data structure,
+ * parameter attributes described by ethtool data structure,
  * ethtool_pauseparam.
  *
  * @param port_id
@@ -209,7 +209,7 @@ int rte_ethtool_get_pauseparam(uint16_t port_id,
 
 /**
  * Setting the Ethernet device pause frame configuration according to
- * parameter attributes desribed by ethtool data structure, ethtool_pauseparam.
+ * parameter attributes described by ethtool data structure, ethtool_pauseparam.
  *
  * @param port_id
  *   The port identifier of the Ethernet device.
-- 
2.20.1


  parent reply	other threads:[~2019-07-01 18:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 18:25 [dpdk-dev] [PATCH 00/30] fix spelling errors in comments and messages Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 01/30] lpm: fix spelling errors Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 02/30] eal/windows: fix comment about fnmatch Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 03/30] bsd/eal: fix spelling error Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 04/30] eal: fix spelling errors Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 05/30] bpf: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 06/30] power: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 07/30] ipsec: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 08/30] acl: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 09/30] bbdev: fix spelling error Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 10/30] eventdev: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 11/30] ethdev: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 12/30] ip_frag: " Stephen Hemminger
2019-07-02 15:07   ` Trybula, ArturX
2019-07-02 15:14   ` Trybula, ArturX
2019-07-01 18:25 ` [dpdk-dev] [PATCH 13/30] examples/multi_process: fix spelling errors Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 14/30] examples/l3fwd: fix misspelling of destination Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 15/30] examples/performance-thread: fix spelling errors Stephen Hemminger
2019-07-01 18:25 ` Stephen Hemminger [this message]
2019-07-02 15:42   ` [dpdk-dev] [PATCH 16/30] examples/ethtool: " Trybula, ArturX
2019-07-01 18:25 ` [dpdk-dev] [PATCH 17/30] examples/vmdq: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 18/30] examples/bond: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 19/30] examples/l3fwd-power: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 20/30] examples/netmap_compat: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 21/30] examples/packet_ordering: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 22/30] examples/service_cores: " Stephen Hemminger
2019-07-02 15:51   ` Trybula, ArturX
2019-07-01 18:25 ` [dpdk-dev] [PATCH 23/30] examples/vhost: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 24/30] examples/vhost_scsi: " Stephen Hemminger
2019-07-02 16:01   ` Trybula, ArturX
2019-07-01 18:25 ` [dpdk-dev] [PATCH 25/30] examples/tep_termination: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 26/30] examples/vm_power_manager: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 27/30] test-pmd: " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 28/30] test: fix multiple " Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 29/30] proc-info: fix spelling error Stephen Hemminger
2019-07-01 18:25 ` [dpdk-dev] [PATCH 30/30] test-compress-perf: fix spelling errors Stephen Hemminger
2019-07-01 18:53 ` [dpdk-dev] [PATCH 00/30] fix spelling errors in comments and messages David Marchand
2019-07-16 11:07 ` Thomas Monjalon
2019-07-31 14:11   ` Thomas Monjalon

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=20190701182536.20110-17-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.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 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.