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_vf_rss:add nic carlsville.
Date: Mon, 20 Apr 2020 05:00:16 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC0D0B8@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1586839123-250215-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 12:39 PM
> To: dts@dpdk.org
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts] [PATCH v1]tests/TestSuite_vf_rss: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_vf_rss.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_vf_rss.py b/tests/TestSuite_vf_rss.py index
> 002c37e..e4637d8 100644
> --- a/tests/TestSuite_vf_rss.py
> +++ b/tests/TestSuite_vf_rss.py
> @@ -234,7 +234,7 @@ class TestVfRss(TestCase):
>
> self.verify(
> self.nic in ["redrockcanyou", "atwood", "boulderrapid",
> "fortville_eagle", "fortville_spirit",
> - "fortville_spirit_single", "fortville_25g", "sageville",
> "sagepond", "fortpark_TLV"],
> + "fortville_spirit_single", "fortville_25g",
> + "sageville", "sagepond", "fortpark_TLV", "carlsville"],
> "NIC Unsupported: " + str(self.nic))
> self.dut_ports = self.dut.get_ports(self.nic)
> self.verify(len(self.dut_ports) >= 1, "Not enough ports available")
> --
> 2.17.1
prev parent reply other threads:[~2020-04-20 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 4:38 Xu,Hailin
2020-04-20 5:00 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC0D0B8@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).