test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Zhang, YanX A" <yanx.a.zhang@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhang, YanX A" <yanx.a.zhang@intel.com>
Subject: Re: [dts] [PATCH V1] tests/TestSuite_runtime_vf_queue_number_kernel:Add support NIC
Date: Wed, 7 Aug 2019 09:29:22 +0000	[thread overview]
Message-ID: <2C49E4B25FAD1D419F7564D633EF72E1F3F95B@SHSMSX105.ccr.corp.intel.com> (raw)
In-Reply-To: <1565170395-132994-1-git-send-email-yanx.a.zhang@intel.com>

Tested-by:  Zhang, YanX A <yanx.a.zhang@intel.com>

-----Original Message-----
From: Zhang, YanX A 
Sent: Wednesday, August 7, 2019 5:33 PM
To: dts@dpdk.org
Cc: Zhang, YanX A <yanx.a.zhang@intel.com>
Subject: [dts][PATCH V1] tests/TestSuite_runtime_vf_queue_number_kernel:Add support NIC

Add support for fortpark_TLV NIC.

Signed-off-by: zhang,yan <yanx.a.zhang@intel.com>
---
 tests/TestSuite_runtime_vf_queue_number_kernel.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/TestSuite_runtime_vf_queue_number_kernel.py b/tests/TestSuite_runtime_vf_queue_number_kernel.py
index 18b72b3..6b64cfd 100644
--- a/tests/TestSuite_runtime_vf_queue_number_kernel.py
+++ b/tests/TestSuite_runtime_vf_queue_number_kernel.py
@@ -50,7 +50,7 @@ class TestRuntimeVfQueueNumberKernel(TestCase):
     max_queue = 16
 
     def set_up_all(self):
-        self.verify(self.nic in ["fortville_eagle", "fortville_spirit", "fortville_25g", "fortville_spirit_single"],
+        self.verify(self.nic in ["fortville_eagle", "fortville_spirit", "fortville_25g", "fortville_spirit_single", "fortpark_TLV"],
                     "Only supported by Fortville")
         self.dut_ports = self.dut.get_ports(self.nic)
         self.verify(len(self.dut_ports) > 1, "Insufficient ports")
-- 
2.17.2


  reply	other threads:[~2019-08-07  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  9:33 zhang,yan
2019-08-07  9:29 ` Zhang, YanX A [this message]
2019-08-12  6:44 ` Tu, Lijuan

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=2C49E4B25FAD1D419F7564D633EF72E1F3F95B@SHSMSX105.ccr.corp.intel.com \
    --to=yanx.a.zhang@intel.com \
    --cc=dts@dpdk.org \
    /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).