From: Mark Kavanagh <mark.b.kavanagh@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/1] doc: fix errors in pdump doc
Date: Thu, 6 Oct 2016 11:36:36 +0100 [thread overview]
Message-ID: <1475750196-14118-1-git-send-email-mark.b.kavanagh@intel.com> (raw)
- Fix copy/paste error in description of how to capture both rx
& tx traffic in a single pcap file
- Replace duplicate word with what original author presumably
intended, such that description now makes sense
Signed-off-by: Mark Kavanagh <mark.b.kavanagh@intel.com>
---
doc/guides/sample_app_ug/pdump.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/sample_app_ug/pdump.rst b/doc/guides/sample_app_ug/pdump.rst
index ac0e7c9..320c914 100644
--- a/doc/guides/sample_app_ug/pdump.rst
+++ b/doc/guides/sample_app_ug/pdump.rst
@@ -119,8 +119,8 @@ Can be either a pcap file name or any Linux iface.
* To receive ingress and egress packets separately ``rx-dev`` and ``tx-dev``
should both be passed with the different file names or the Linux iface names.
- * To receive ingress and egress packets separately ``rx-dev`` and ``tx-dev``
- should both be passed with the same file names or the the Linux iface names.
+ * To receive ingress and egress packets together, ``rx-dev`` and ``tx-dev``
+ should both be passed with the same file name or the same Linux iface name.
``ring-size``:
Size of the ring. This value is used internally for ring creation. The ring will be used to enqueue the packets from
--
1.9.3
next reply other threads:[~2016-10-06 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 10:36 Mark Kavanagh [this message]
2016-10-06 21:01 ` Mcnamara, John
2016-10-13 16:19 ` 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=1475750196-14118-1-git-send-email-mark.b.kavanagh@intel.com \
--to=mark.b.kavanagh@intel.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).