From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, bernard.iremonger@intel.com,
jingjing.wu@intel.com, wenzhuo.lu@intel.com,
john.mcnamara@intel.com, Shreyansh Jain <shreyansh.jain@nxp.com>,
stable@dpdk.org
Subject: [dpdk-dev] [PATCH v2] doc: fix incorrect create bonding command in testpmd
Date: Wed, 25 Jul 2018 17:01:32 +0530 [thread overview]
Message-ID: <20180725113132.1111-1-shreyansh.jain@nxp.com> (raw)
In-Reply-To: <20180723112739.24293-1-shreyansh.jain@nxp.com>
Fixes: ac718398f477 ("doc: testpmd application user guide")
Cc: bernard.iremonger@intel.com
Cc: stable@dpdk.org
Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
v2:
Update the Fixes line to represent the first commit
rather than the formatting patch (e76d7a76).
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 1d6bdf9b3..16af95035 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -1993,7 +1993,7 @@ Create a new bonding device::
For example, to create a bonded device in mode 1 on socket 0::
- testpmd> create bonded 1 0
+ testpmd> create bonded device 1 0
created new bonded device (port X)
add bonding slave
--
2.17.1
next prev parent reply other threads:[~2018-07-25 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 11:27 [dpdk-dev] [PATCH] " Shreyansh Jain
2018-07-23 20:49 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2018-07-25 9:00 ` Iremonger, Bernard
2018-07-25 11:31 ` Shreyansh Jain [this message]
2018-07-26 20:36 ` [dpdk-dev] [PATCH v2] " 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=20180725113132.1111-1-shreyansh.jain@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.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).