DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trybula, ArturX" <arturx.trybula@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH 12/30] ip_frag: fix spelling error
Date: Tue, 2 Jul 2019 15:07:14 +0000	[thread overview]
Message-ID: <5B6D1C77E9D7034C93E97BD83D1D9F57077DD82C@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <20190701182536.20110-13-stephen@networkplumber.org>



-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
Sent: Monday, July 1, 2019 20:25
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 12/30] ip_frag: fix spelling error

Spelling errors found by codespell.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 examples/ip_fragmentation/main.c         | 2 +-
 lib/librte_ip_frag/rte_ipv4_reassembly.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/examples/ip_fragmentation/main.c b/examples/ip_fragmentation/main.c
index 85c0100f792d..eb6ca097aa7e 100644
--- a/examples/ip_fragmentation/main.c
+++ b/examples/ip_fragmentation/main.c
@@ -635,7 +635,7 @@ check_all_ports_link_status(uint32_t port_mask)
 	}
 }
 
-/* Check L3 packet type detection capablity of the NIC port */
+/* Check L3 packet type detection capability of the NIC port */
 static int
 check_ptype(int portid)
 {
diff --git a/lib/librte_ip_frag/rte_ipv4_reassembly.c b/lib/librte_ip_frag/rte_ipv4_reassembly.c
index b7b92ed28549..28003e42af63 100644
--- a/lib/librte_ip_frag/rte_ipv4_reassembly.c
+++ b/lib/librte_ip_frag/rte_ipv4_reassembly.c
@@ -83,7 +83,7 @@ ipv4_frag_reassemble(struct ip_frag_pkt *fp)
 
 /*
  * Process new mbuf with fragment of IPV4 packet.
- * Incoming mbuf should have it's l2_len/l3_len fields setuped correclty.
+ * Incoming mbuf should have it's l2_len/l3_len fields setuped correctly.

[Artur] should be without apostrophe:  "... have its ...." 

  * @param tbl
  *   Table where to lookup /add the fragmented packet.
  * @param mb
-- 
2.20.1


  reply	other threads:[~2019-07-02 15:53 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 [this message]
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 ` [dpdk-dev] [PATCH 16/30] examples/ethtool: " Stephen Hemminger
2019-07-02 15:42   ` 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=5B6D1C77E9D7034C93E97BD83D1D9F57077DD82C@HASMSX110.ger.corp.intel.com \
    --to=arturx.trybula@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).