From: Pavel Shirshov <pavel.shirshov@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] lib/librte_pipeline: Fix a typo
Date: Fri, 10 Nov 2017 00:17:27 -0800 [thread overview]
Message-ID: <1510301847-18725-1-git-send-email-pavel.shirshov@gmail.com> (raw)
Signed-off-by: Pavel Shirshov <pavel.shirshov@gmail.com>
---
lib/librte_pipeline/rte_pipeline.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_pipeline/rte_pipeline.h b/lib/librte_pipeline/rte_pipeline.h
index f366348..fdc44a7 100644
--- a/lib/librte_pipeline/rte_pipeline.h
+++ b/lib/librte_pipeline/rte_pipeline.h
@@ -483,7 +483,7 @@ int rte_pipeline_table_entry_delete(struct rte_pipeline *p,
* @param keys
* Array containing table entry keys
* @param entries
- * Array containung new contents for every table entry identified by key
+ * Array containing new contents for every table entry identified by key
* @param n_keys
* Number of keys to add
* @param key_found
--
2.7.4
next reply other threads:[~2017-11-10 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 8:17 Pavel Shirshov [this message]
2017-11-10 11:11 ` Dumitrescu, Cristian
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=1510301847-18725-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).