From: Rami Rosen <rami.rosen@intel.com>
To: yong.liu@intel.com
Cc: dts@dpdk.org, Rami Rosen <rami.rosen@intel.com>
Subject: [dts] [PATCH] test_plans vf&pf reset: use the correct VFs IDs.
Date: Fri, 25 Aug 2017 01:30:09 +0300 [thread overview]
Message-ID: <20170824223009.22099-1-rami.rosen@intel.com> (raw)
This patch fixes the first test case in the vf_pf
reset test plan to use the correct VFs IDs.
Since we create two VFs using 0000:81:00.0, the VFs are
81:02.0, 81:02.1 and not 82:02.0, 82:02.1.
Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
test_plans/vf_pf_reset_test_plan.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test_plans/vf_pf_reset_test_plan.rst b/test_plans/vf_pf_reset_test_plan.rst
index 3a939bbc55d2..f59ab817805e 100644
--- a/test_plans/vf_pf_reset_test_plan.rst
+++ b/test_plans/vf_pf_reset_test_plan.rst
@@ -75,7 +75,7 @@ Test Case 1: vf reset -- create two vfs on one pf
3. Bind the VFs to dpdk driver::
- ./tools/dpdk-devbind.py -b vfio-pci 82:02.0 82:02.1
+ ./tools/dpdk-devbind.py -b vfio-pci 81:02.0 81:02.1
4. Set the VLAN id of VF1 and VF2::
--
2.11.0
next reply other threads:[~2017-08-24 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 22:30 Rami Rosen [this message]
2017-08-25 11:27 ` 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=20170824223009.22099-1-rami.rosen@intel.com \
--to=rami.rosen@intel.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).