From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1] tests/userspace_ethtool: cannot change CVL link status by the peer port
Date: Fri, 22 Nov 2019 02:55:54 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB663FE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1572530838-44694-1-git-send-email-wenjiex.a.li@intel.com>
Applied failed, please rework your patch
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Thursday, October 31, 2019 10:07 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V1] tests/userspace_ethtool: cannot change CVL link
> status by the peer port
>
> In case dump_driver_info, like fortville, CVL link status cannot be changed by
> the peer ports.
> After change the peer port status by running "ip link set dev PORT
> down|up", CVL link status will not change. So skip this step.
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> tests/TestSuite_userspace_ethtool.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_userspace_ethtool.py
> b/tests/TestSuite_userspace_ethtool.py
> index 116fd3a..8d18b0c 100644
> --- a/tests/TestSuite_userspace_ethtool.py
> +++ b/tests/TestSuite_userspace_ethtool.py
> @@ -259,7 +259,7 @@ class TestUserspaceEthtool(TestCase,
> IxiaPacketGenerator):
> # only detect physical link disconnect status
> verify_pass = True
> verify_msg = ''
> - if self.nic.startswith("fortville") == False:
> + if self.nic.startswith("fortville") == False and
> self.nic.startswith("columbiaville") == False:
> # check link status dump function
> for port in self.ports:
> tester_port = self.tester.get_local_port(port)
> --
> 2.17.1
prev parent reply other threads:[~2019-11-22 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 14:07 Wenjie Li
2019-10-31 5:22 ` Zhu, WenhuiX
2019-11-22 2: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=8CE3E05A3F976642AAB0F4675D0AD20E0BB663FE@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=wenjiex.a.li@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).