From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>,
"Mei, JianweiX" <jianweix.mei@intel.com>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V1 1/1] tests/dcf_lifecycle: support 4 ports
Date: Mon, 20 Jul 2020 06:55:28 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC82154@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200703025558.24388-2-yufengx.mo@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of yufengmx
> Sent: 2020年7月3日 10:56
> To: dts@dpdk.org; Mei, JianweiX <jianweix.mei@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V1 1/1] tests/dcf_lifecycle: support 4 ports
>
>
> support 4 ports.
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> tests/TestSuite_dcf_lifecycle.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_dcf_lifecycle.py b/tests/TestSuite_dcf_lifecycle.py
> index 90a56e6..3971941 100644
> --- a/tests/TestSuite_dcf_lifecycle.py
> +++ b/tests/TestSuite_dcf_lifecycle.py
> @@ -249,7 +249,7 @@ class TestDcfLifeCycle(TestCase):
> pf1_vf1 = self.vf_ports_info[0].get('vfs_pci')[1]
> pf1_vf2 = self.vf_ports_info[0].get('vfs_pci')[2]
> pf2_vf0 = self.vf_ports_info[1].get('vfs_pci')[0] \
> - if len(self.vf_ports_info) == 2 else ''
> + if len(self.vf_ports_info) >= 2 else ''
> whitelist = {
> 'pf1_vf0_dcf': f"-w {pf1_vf0},cap=dcf",
> 'pf1_vf1_dcf': f"-w {pf1_vf1},cap=dcf",
> --
> 2.21.0
prev parent reply other threads:[~2020-07-20 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 2:55 [dts] [PATCH V1 0/1] " yufengmx
2020-07-03 2:55 ` [dts] [PATCH V1 1/1] " yufengmx
2020-07-20 6:55 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC82154@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=jianweix.mei@intel.com \
--cc=yufengx.mo@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).