From: "huilong,xu" <huilongx.xu@intel.com>
To: dts@dpdk.org
Subject: [dts] [dts 1/4] [PATCH V1] add dual vlan test case in default execution file
Date: Wed, 27 May 2015 15:02:02 +0800 [thread overview]
Message-ID: <1432710125-23668-1-git-send-email-huilongx.xu@intel.com> (raw)
From: huilong xu <huilongx.xu@intel.com>
changed list:
1. add dual vlan for niantic and fortville test
2. add vlan for fortville test
Signed-off-by: huilong xu <huilongx.xu@intel.com>
---
executions/execution.cfg | 3 ++-
executions/execution_FVL.cfg | 4 +++-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/executions/execution.cfg b/executions/execution.cfg
index 73d70f6..e5c6198 100644
--- a/executions/execution.cfg
+++ b/executions/execution.cfg
@@ -18,7 +18,8 @@ test_suites=
ip_pipeline,
pmd_bonded,
dynamic_config,
- generic_filter
+ generic_filter,
+ dual_vlan
targets=
x86_64-native-linuxapp-gcc
parameters=nic_type=cfg:func=true
diff --git a/executions/execution_FVL.cfg b/executions/execution_FVL.cfg
index 7e5151b..12990d8 100644
--- a/executions/execution_FVL.cfg
+++ b/executions/execution_FVL.cfg
@@ -4,7 +4,9 @@ drivername=<driver name igb_uio or vfio-pci>
test_suites=
checksum_offload,
dynamic_config,
- generic_filter
+ generic_filter,
+ dual_vlan,
+ vlan
targets=
x86_64-native-linuxapp-gcc
parameters=nic_type=cfg:func=true
--
1.7.4.4
next reply other threads:[~2015-05-27 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 7:02 huilong,xu [this message]
2015-05-27 7:02 ` [dts] [dts 2/4] [PATCH V1] add dual vlan test plan huilong,xu
2015-05-27 7:02 ` [dts] [dts 3/4] [PATCH v1] add dual vlan test case huilong,xu
2015-05-27 7:02 ` [dts] [dts 4/4] [PATCH V1] update vlan get package function huilong,xu
2015-06-01 9:12 ` [dts] [dts 1/4] [PATCH V1] add dual vlan test case in default execution file 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=1432710125-23668-1-git-send-email-huilongx.xu@intel.com \
--to=huilongx.xu@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).