From: Rami Rosen <rami.rosen@intel.com>
To: dts@dpdk.org
Cc: Rami Rosen <rami.rosen@intel.com>
Subject: [dts] [PATCH] test_plans: userspace_ethtool: fix to use a correct filename.
Date: Fri, 26 Aug 2016 03:53:33 +0300 [thread overview]
Message-ID: <1472172813-26188-1-git-send-email-rami.rosen@intel.com> (raw)
This patch fixes the retrieve register test to use the correct
filename.
Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
test_plans/userspace_ethtool_test_plan.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test_plans/userspace_ethtool_test_plan.rst b/test_plans/userspace_ethtool_test_plan.rst
index 83e7fac..b9593eb 100644
--- a/test_plans/userspace_ethtool_test_plan.rst
+++ b/test_plans/userspace_ethtool_test_plan.rst
@@ -119,7 +119,7 @@ Unbind ports from igb_uio and bind them to default driver.
Check that dumped register information is correct.
ethtool -d INTF_0 raw off file reg_0.bin
-ethtool -d INTF_1 raw off file reg_0.bin
+ethtool -d INTF_1 raw off file reg_1.bin
Test Case: Ring param test
==========================
--
2.7.4
reply other threads:[~2016-08-26 1:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1472172813-26188-1-git-send-email-rami.rosen@intel.com \
--to=rami.rosen@intel.com \
--cc=dts@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).