test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Wang, Yinan" <yinan.wang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, Yinan" <yinan.wang@intel.com>
Subject: Re: [dts] [PATCH v2] tests/vf_interrupt_pmd:add more supported nic type
Date: Tue, 25 Feb 2020 01:28:03 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBCDB83@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200223215036.66321-1-yinan.wang@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Monday, February 24, 2020 5:51 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v2] tests/vf_interrupt_pmd:add more supported nic
> type
> 
> From: Wang Yinan <yinan.wang@intel.com>
> 
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
>  tests/TestSuite_vf_interrupt_pmd.py | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/TestSuite_vf_interrupt_pmd.py
> b/tests/TestSuite_vf_interrupt_pmd.py
> index 21b24a1..42dfc02 100644
> --- a/tests/TestSuite_vf_interrupt_pmd.py
> +++ b/tests/TestSuite_vf_interrupt_pmd.py
> @@ -319,7 +319,8 @@ class TestVfInterruptPmd(TestCase):
>          """
>          Check Interrupt for VF with vfio driver, need test with i40e driver
>          """
> -        self.verify(self.nic in ("fortville_spirit"), "the port can not run this suite")
> +        self.verify(self.nic in ["fortville_eagle", "fortville_spirit",
> +                                 "fortville_spirit_single", "fortpark_TLV"], "%s nic port not
> support vf multi-queues interrupt" % self.nic)
>          self.queues = 4
>          self.prepare_l3fwd_power(self.dut)
>          self.set_NIC_link()
> @@ -349,7 +350,8 @@ class TestVfInterruptPmd(TestCase):
>          """
>          Check for interrupts within the VM, need test with i40e driver
>          """
> -        self.verify(self.nic in ("fortville_spirit"), "the port can not run this suite")
> +        self.verify(self.nic in ["fortville_eagle", "fortville_spirit",
> +                                 "fortville_spirit_single", "fortpark_TLV"], "%s nic not supp
> ort vf multi-queues interrupt" % self.nic)
>          self.setup_vm_env()
>          self.vm0_dut.send_expect("ip link set %s vf 0 mac %s" %
>                                   (self.host_intf0, self.vf0_mac), "# ")
> --
> 2.17.1


      reply	other threads:[~2020-02-25  1:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 21:50 Yinan
2020-02-25  1:28 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BBCDB83@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yinan.wang@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).