From: Pavel Shirshov <pavel.shirshov@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] lib/librte_gso: Fix a typo
Date: Thu, 9 Nov 2017 23:54:40 -0800 [thread overview]
Message-ID: <1510300480-16675-1-git-send-email-pavel.shirshov@gmail.com> (raw)
Signed-off-by: Pavel Shirshov <pavel.shirshov@gmail.com>
---
lib/librte_gso/rte_gso.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_gso/rte_gso.h b/lib/librte_gso/rte_gso.h
index 4b77176..dbaedec 100644
--- a/lib/librte_gso/rte_gso.h
+++ b/lib/librte_gso/rte_gso.h
@@ -103,7 +103,7 @@ struct rte_gso_ctx {
* Before calling rte_gso_segment(), applications must set proper ol_flags
* for the packet. The GSO library uses the same macros as that of TSO.
* For example, set PKT_TX_TCP_SEG and PKT_TX_IPV4 in ol_flags to segment
- * a TCP/IPv4 packet. If rte_gso_segment() succceds, the PKT_TX_TCP_SEG
+ * a TCP/IPv4 packet. If rte_gso_segment() succeeds, the PKT_TX_TCP_SEG
* flag is removed for all GSO segments and the input packet.
*
* Each of the newly-created GSO segments is organized as a two-segment
--
2.7.4
reply other threads:[~2017-11-10 7:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1510300480-16675-1-git-send-email-pavel.shirshov@gmail.com \
--to=pavel.shirshov@gmail.com \
--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 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).