test suite reviews and discussions
 help / color / mirror / Atom feed
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_vxlan_sample:add nic carlsville.
Date: Mon, 20 Apr 2020 05:12:49 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC0D1D2@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1586855288-294329-1-git-send-email-hailinx.xu@intel.com>

Applied failed, please rework ,thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xu,Hailin
> Sent: Tuesday, April 14, 2020 5:08 PM
> To: dts@dpdk.org
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts] [PATCH v1]tests/TestSuite_vxlan_sample:add nic carlsville.
> 
> From: xuhailin <hailinx.xu@intel.com>
> 
> carlsville driver is i40e, so the nic support the suite.
> 
> Signed-off-by: xuhailin <hailinx.xu@intel.com>
> ---
>  tests/TestSuite_vxlan_sample.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/TestSuite_vxlan_sample.py
> b/tests/TestSuite_vxlan_sample.py index 4ab9f18..71f49b4 100644
> --- a/tests/TestSuite_vxlan_sample.py
> +++ b/tests/TestSuite_vxlan_sample.py
> @@ -78,7 +78,7 @@ class TestVxlanSample(TestCase):
> 
>          # this feature only enable in FVL now
>          self.verify(self.nic in ["fortville_eagle", "fortville_spirit",
> -                                 "fortville_spirit_single", "fortpark_TLV", "fortville_25g"],
> +                                 "fortville_spirit_single",
> + "fortpark_TLV", "fortville_25g", "carlsville"],
>                      "Vxlan Only supported by Fortville")
>          # Based on h/w type, choose how many ports to use
>          self.dut_ports = self.dut.get_ports()
> --
> 2.17.1


      parent reply	other threads:[~2020-04-20  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  9:08 Xu,Hailin
2020-04-17  3:21 ` Zhao, XinfengX
2020-04-20  5:12 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC0D1D2@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).