From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V1 5/6] test_plan/cvl_switch_filter_pppoe: update test plan for dpdk code change
Date: Fri, 29 Oct 2021 14:18:28 +0800 [thread overview]
Message-ID: <1635488309-118246-5-git-send-email-songx.jiale@intel.com> (raw)
In-Reply-To: <1635488309-118246-1-git-send-email-songx.jiale@intel.com>
dpdk invalid port create rule echo change
dpdk commit: 1179f05cc9a044541106981b0366f474043d7872
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
test_plans/cvl_switch_filter_pppoe_test_plan.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
mode change 100644 => 100755 test_plans/cvl_switch_filter_pppoe_test_plan.rst
diff --git a/test_plans/cvl_switch_filter_pppoe_test_plan.rst b/test_plans/cvl_switch_filter_pppoe_test_plan.rst
old mode 100644
new mode 100755
index b9e04ea6..4f3da525
--- a/test_plans/cvl_switch_filter_pppoe_test_plan.rst
+++ b/test_plans/cvl_switch_filter_pppoe_test_plan.rst
@@ -5748,7 +5748,7 @@ Subcase 13: invalid port
Failed to create flow, report message::
- No such device: No such device
+ Invalid port 1
2. check the rule list on port 0::
@@ -5857,7 +5857,7 @@ Note: some of the error messages may be different.
get the error message::
- No such device: No such device
+ Invalid port 1
11. check the rule list::
--
2.17.1
next prev parent reply other threads:[~2021-10-29 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 6:18 [dts] [PATCH V1 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: update case code " Jiale Song
2021-10-29 6:18 ` [dts] [PATCH V1 2/6] tests/cvl_advanced_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-10-29 6:18 ` [dts] [PATCH V1 3/6] tests/cvl_fdir: " Jiale Song
2021-10-29 6:18 ` [dts] [PATCH V1 4/6] tests/flow_classify_softnic: " Jiale Song
2021-10-29 6:18 ` Jiale Song [this message]
2021-10-29 6:18 ` [dts] [PATCH V1 6/6] test_plans/iavf_fdir: update test plan " Jiale Song
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=1635488309-118246-5-git-send-email-songx.jiale@intel.com \
--to=songx.jiale@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).