From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "nareddy@marvell.com" <nareddy@marvell.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "fmasood@marvell.com" <fmasood@marvell.com>,
"avijay@marvell.com" <avijay@marvell.com>
Subject: Re: [dts] [PATCH v2] TestSuite_dual_vlan.py : vlan_stripq_config is not supported for cavium_a063
Date: Tue, 23 Apr 2019 20:40:23 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA659F3@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1556000847-24681-1-git-send-email-nareddy@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of
> nareddy@marvell.com
> Sent: Monday, April 22, 2019 11:27 PM
> To: dts@dpdk.org
> Cc: fmasood@marvell.com; avijay@marvell.com; Praneeth Reddy
> <nareddy@marvell.com>
> Subject: [dts] [PATCH v2] TestSuite_dual_vlan.py : vlan_stripq_config is not
> supported for cavium_a063
>
> From: Praneeth Reddy <nareddy@marvell.com>
>
> rx_vlan_strip_set_on_queue is not supported for cavium_a063.
> Adding cavium_a063 to unsupported to list.
>
> Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
> ---
> conf/test_case_checklist.json | 3 ++-
> tests/TestSuite_dual_vlan.py | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index a1aa90b..239cd89 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -265,7 +265,8 @@
> "kawela_4",
> "springville",
> "fortville_25g",
> - "fortpark_TLV"
> + "fortpark_TLV",
> + "cavium_a063"
> ],
> "Target": [
> "ALL"
> diff --git a/tests/TestSuite_dual_vlan.py b/tests/TestSuite_dual_vlan.py
> index 405a5a2..63bb715 100644
> --- a/tests/TestSuite_dual_vlan.py
> +++ b/tests/TestSuite_dual_vlan.py
> @@ -338,7 +338,7 @@ class TestDualVlan(TestCase):
> """
> Enable/Disable VLAN packets strip on queue
> """
> - self.verify(self.nic not in ["fortville_eagle", "fortville_spirit",
> "fortville_spirit_single", "fortville_25g", "fortpark_TLV"], "%s NIC not support
> queue vlan strip " % self.nic)
> + self.verify(self.nic not in ["fortville_eagle",
> + "fortville_spirit", "fortville_spirit_single", "fortville_25g",
> + "fortpark_TLV", "cavium_a063"], "%s NIC not support queue vlan strip "
> + % self.nic)
>
> self.mode_config(filter="off")
> self.mode_config(qinq="off")
> --
> 1.8.3.1
prev parent reply other threads:[~2019-04-23 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 6:04 [dts] [PATCH] " nareddy
2019-04-23 6:24 ` [dts] [PATCH v2] " nareddy
2019-04-23 6:28 ` Narala Praneeth Reddy
2019-04-23 6:27 ` nareddy
2019-04-23 20:40 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BA659F3@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=nareddy@marvell.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).