All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Magistro <koncept1@gmail.com>
To: dev@dpdk.org
Cc: ben.magistro@trinitycyber.com, stable@dpdk.org,
	stephen@networkplumber.org, Ben Magistro <koncept1@gmail.com>
Subject: [PATCH] apps/dumpcap: fix interface parameter option
Date: Sun, 21 Aug 2022 23:56:18 +0000	[thread overview]
Message-ID: <20220821235617.2628-1-koncept1@gmail.com> (raw)

The dumpcap application supports an interface parameter via the
`-i` [1] option however the current documentation utilizes a `-I` flag.

[1] https://git.dpdk.org/dpdk/tree/app/dumpcap/main.c#n314

Fixes: cbb44143be74 ("app/dumpcap: add new packet capture application")
Cc: stable@dpdk.org

Signed-off-by: Ben Magistro <koncept1@gmail.com>
---
 doc/guides/tools/dumpcap.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/tools/dumpcap.rst b/doc/guides/tools/dumpcap.rst
index 6fa284380c..d8a137b1cd 100644
--- a/doc/guides/tools/dumpcap.rst
+++ b/doc/guides/tools/dumpcap.rst
@@ -43,7 +43,7 @@ To list interfaces available for capture, use ``--list-interfaces``.
 
 To filter packets in style of *tshark*, use the ``-f`` flag.
 
-To capture on multiple interfaces at once, use multiple ``-I`` flags.
+To capture on multiple interfaces at once, use multiple ``-i`` flags.
 
 
 Example
@@ -55,7 +55,7 @@ Example
    0. 000:00:03.0
    1. 000:00:03.1
 
-   # <build_dir>/app/dpdk-dumpcap -I 0000:00:03.0 -c 6 -w /tmp/sample.pcapng
+   # <build_dir>/app/dpdk-dumpcap -i 0000:00:03.0 -c 6 -w /tmp/sample.pcapng
    Packets captured: 6
    Packets received/dropped on interface '0000:00:03.0' 6/0
 
-- 
2.27.0


             reply	other threads:[~2022-08-21 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 23:56 Ben Magistro [this message]
2022-10-10  0:11 ` [PATCH] apps/dumpcap: fix interface parameter option 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=20220821235617.2628-1-koncept1@gmail.com \
    --to=koncept1@gmail.com \
    --cc=ben.magistro@trinitycyber.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --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 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.