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_vm_hotplug:add nic carlsville
Date: Mon, 27 Apr 2020 07:50:39 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC12A23@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1587718350-96542-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: Friday, April 24, 2020 4:53 PM
> To: dts@dpdk.org
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts] [PATCH v1] tests/TestSuite_vm_hotplug: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_vm_hotplug.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/TestSuite_vm_hotplug.py b/tests/TestSuite_vm_hotplug.py
> index 35c3bb1..45cfc89 100644
> --- a/tests/TestSuite_vm_hotplug.py
> +++ b/tests/TestSuite_vm_hotplug.py
> @@ -292,7 +292,7 @@ class TestVmHotplug(TestCase):
>          time.sleep(1)
>          sign = 'Connection'
>          lis1 = ['fortville_spirit', 'fortville_eagle', 'sagepond', 'twinpond',
> 'sageville']
> -        lis2 = ['fortpark_TLV', 'fortville_25g',"fortpark_BASE-T"]
> +        lis2 = ['fortpark_TLV', 'fortville_25g',"fortpark_BASE-T",
> + "carlsville"]
>          if self.nic in lis1:
>              sign = 'Ethernet'
>          elif self.nic in lis2:
> --
> 1.8.3.1


      parent reply	other threads:[~2020-04-27  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  8:52 Xu, Hailin
2020-04-24  9:07 ` Xu, HailinX
2020-04-27  7:50 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC12A23@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).