From: Rami Rosen <ramirose@gmail.com>
To: dev@dpdk.org
Cc: bernard.iremonger@intel.com, stable@dpdk.org,
Rami Rosen <ramirose@gmail.com>
Subject: [PATCH] doc: fix a typo in testpmd guide
Date: Mon, 3 Dec 2018 20:25:38 +0200 [thread overview]
Message-ID: <20181203182538.4426-1-ramirose@gmail.com> (raw)
This patch fixes a typo in testpmd guide (should be ICMP and not IMCP)
Fixes: ac718398f477 ("doc: testpmd application user guide")
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 056f8bb32..63e4a2d19 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -318,7 +318,7 @@ The available information categories are:
* ``csum``: Changes the checksum field with hardware or software methods depending on the offload flags on the packet.
-* ``icmpecho``: Receives a burst of packets, lookup for IMCP echo requests and, if any, send back ICMP echo replies.
+* ``icmpecho``: Receives a burst of packets, lookup for ICMP echo requests and, if any, send back ICMP echo replies.
* ``ieee1588``: Demonstrate L2 IEEE1588 V2 PTP timestamping for RX and TX. Requires ``CONFIG_RTE_LIBRTE_IEEE1588=y``.
--
2.19.1
next reply other threads:[~2018-12-03 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 18:25 Rami Rosen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-01 6:14 [PATCH] doc: fix a typo in testpmd guide Rami Rosen
2018-12-02 17:44 ` Iremonger, Bernard
2018-12-03 17:22 ` Iremonger, Bernard
2017-09-23 16:55 Rami Rosen
2017-09-25 1:59 ` Xing, Beilei
2017-09-25 11:21 ` Mcnamara, John
2017-10-05 15:15 ` 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=20181203182538.4426-1-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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.