From: "Wu, ChangqingX" <changqingx.wu@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V2] tests/userspace_ethtool:remove the Vlan filter offload flag bit.
Date: Mon, 14 Jan 2019 03:00:38 +0000 [thread overview]
Message-ID: <7F81DD3887C58F49A6B2EFEC3C28E22E0B68E6C7@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1547431277-31668-1-git-send-email-shuaix.zhu@intel.com>
Tested-by: Wu, ChangqingX <changqingx.wu@intel.com>
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
Sent: Monday, January 14, 2019 10:01 AM
To: dts@dpdk.org
Cc: Zhu, ShuaiX <shuaix.zhu@intel.com>
Subject: [dts] [PATCH V2] tests/userspace_ethtool:remove the Vlan filter offload flag bit.
since to changes from 18.02 dpdk, changes about all offload flag in dpdk source code.
‘hw_vlan_filter’ is abandoned since 18.02.
Signed-off-by: zhu,shuai <shuaix.zhu@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 8ade421..a7a2a62 100644
--- a/tests/TestSuite_userspace_ethtool.py
+++ b/tests/TestSuite_userspace_ethtool.py
@@ -467,7 +467,7 @@ class TestUserspaceEthtool(TestCase, IxiaPacketGenerator):
self.verify(tx_pkts_del == rx_pkts, "Failed to remove Rx vlan filter")
self.dut.send_expect("quit", "# ")
- self.dut.send_expect("sed -i -e '/hw_vlan_filter=1;$/d' %s" % main_file, "# ")
+ self.dut.send_expect("sed -i -e '/cfg_port.rxmode.offloads|=DEV_RX_OFFLOAD_VLAN_FILTER;$/d' %s" % main_file, "# ")
# build sample app
self.build_ethtool()
--
2.17.2
next prev parent reply other threads:[~2019-01-14 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 2:01 zhu,shuai
2019-01-14 3:00 ` Wu, ChangqingX [this message]
2019-01-15 5:56 ` 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=7F81DD3887C58F49A6B2EFEC3C28E22E0B68E6C7@SHSMSX101.ccr.corp.intel.com \
--to=changqingx.wu@intel.com \
--cc=dts@dpdk.org \
--cc=shuaix.zhu@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).