From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xu, HailinX" <hailinx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, HailinX" <hailinx.xu@intel.com>
Subject: Re: [dts] [PATCH v1] tests/TestSuite_qinq_filter:add nic carlsville
Date: Thu, 23 Apr 2020 05:42:44 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC0F0D5@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1587467039-274871-1-git-send-email-hailinx.xu@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xu Hailin
> Sent: Tuesday, April 21, 2020 7:04 PM
> To: dts@dpdk.org
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts] [PATCH v1] tests/TestSuite_qinq_filter:add nic carlsville
>
> From: "Xu, Hailin" <hailinx.xu@intel.com>
>
> carlsville driver is i40e, so the nic support the suite.
>
> Signed-off-by: Xu, Hailin <hailinx.xu@intel.com>
> ---
> tests/TestSuite_qinq_filter.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_qinq_filter.py b/tests/TestSuite_qinq_filter.py
> index 4450ea0..de5520d 100644
> --- a/tests/TestSuite_qinq_filter.py
> +++ b/tests/TestSuite_qinq_filter.py
> @@ -51,7 +51,7 @@ class TestQinqFilter(TestCase):
> global dutRxPortId
> global dutTxPortId
>
> - self.verify(self.nic in ["fortville_eagle", "fortville_spirit",
> "fortville_spirit_single", "fortville_25g", 'foxville'],
> + self.verify(self.nic in ["fortville_eagle", "fortville_spirit",
> + "fortville_spirit_single", "fortville_25g", 'foxville', 'carlsville'],
> "NIC %s not support this test" % self.nic)
> print('this case only supports fortville with 6.0.0+ firmware and
> dpdk17.05+')
> ports = self.dut.get_ports()
> --
> 1.8.3.1
next prev parent reply other threads:[~2020-04-23 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 11:03 Xu Hailin
2020-04-23 5:42 ` Tu, Lijuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-21 9:06 Xu, Hailin
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=8CE3E05A3F976642AAB0F4675D0AD20E0BC0F0D5@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=hailinx.xu@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).