From: Muhammad Bilal <m.bilal@emumba.com>
To: jgrajcia@cisco.com
Cc: dev@dpdk.org, Muhammad Bilal <m.bilal@emumba.com>, jmilan.dev@gmail.com
Subject: [dpdk-dev] [PATCH] doc: removed typing mistake
Date: Fri, 29 May 2020 19:47:45 +0500 [thread overview]
Message-ID: <20200529144745.14412-1-m.bilal@emumba.com> (raw)
There was a duplicate command instruction in the documentation of memif
so I have removed the 1 command from it.
Fixes: cbbbbd3365d2 ("net/memif: enable loopback")
Cc: jmilan.dev@gmail.com
Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
---
doc/guides/nics/memif.rst | 1 -
1 file changed, 1 deletion(-)
diff --git a/doc/guides/nics/memif.rst b/doc/guides/nics/memif.rst
index 08a9fda86..ddeebed25 100644
--- a/doc/guides/nics/memif.rst
+++ b/doc/guides/nics/memif.rst
@@ -289,4 +289,3 @@ Then start the communication::
Finally we can check port stats to see the traffic::
testpmd> show port stats all
- testpmd> show port stats all
--
2.17.1
next reply other threads:[~2020-05-29 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 14:47 Muhammad Bilal [this message]
2020-06-02 17:50 ` Ferruh Yigit
2020-09-09 21:39 Muhammad Bilal
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=20200529144745.14412-1-m.bilal@emumba.com \
--to=m.bilal@emumba.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=jmilan.dev@gmail.com \
/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).