From: Rami Rosen <ramirose@gmail.com>
To: yong.liu@intel.com
Cc: dts@dpdk.org, Rami Rosen <ramirose@gmail.com>
Subject: [dts] [PATCH] test_plans/dynamic_queue: fix usage of bind script
Date: Fri, 24 Aug 2018 13:08:34 +0300 [thread overview]
Message-ID: <20180824100834.20086-1-ramirose@gmail.com> (raw)
The dpdk-devbind.py script resides under "usertools" for over a year now,
instead of its previous location, "tools". This script fixes it.
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
test_plans/dynamic_queue_test_plan.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test_plans/dynamic_queue_test_plan.rst b/test_plans/dynamic_queue_test_plan.rst
index 01694d2..6be6ec7 100644
--- a/test_plans/dynamic_queue_test_plan.rst
+++ b/test_plans/dynamic_queue_test_plan.rst
@@ -74,7 +74,7 @@ Prerequisites
=============
1. Host PF in DPDK driver::
- ./tools/dpdk-devbind.py -b igb_uio 81:00.0
+ ./usertools/dpdk-devbind.py -b igb_uio 81:00.0
2. Start testpmd on host, set chained port topology mode, add txq/rxq to
enable multi-queues::
--
2.17.1
next reply other threads:[~2018-08-24 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 10:08 Rami Rosen [this message]
2018-08-27 13:15 ` Liu, Yong
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=20180824100834.20086-1-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=dts@dpdk.org \
--cc=yong.liu@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).