From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org
Cc: qiming.yang@intel.com, qi.z.zhang@intel.com, qi.fu@intel.com,
Haiyue Wang <haiyue.wang@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Beilei Xing <beilei.xing@intel.com>
Subject: [dpdk-dev] [PATCH v3 2/2] net/iavf: align to the new VLAN offload name
Date: Wed, 20 Jan 2021 12:17:49 +0800 [thread overview]
Message-ID: <20210120041750.408535-3-haiyue.wang@intel.com> (raw)
In-Reply-To: <20210120041750.408535-1-haiyue.wang@intel.com>
Since the VLAN offload virtchnl message name has been renamed to setting
style, the internal Ethernet type setting name needs be changed to avoid
confusing.
Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
---
drivers/net/iavf/iavf_vchnl.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/net/iavf/iavf_vchnl.c b/drivers/net/iavf/iavf_vchnl.c
index 426ddb6c7e..c82925eceb 100644
--- a/drivers/net/iavf/iavf_vchnl.c
+++ b/drivers/net/iavf/iavf_vchnl.c
@@ -532,16 +532,16 @@ iavf_config_vlan_strip_v2(struct iavf_adapter *adapter, bool enable)
struct virtchnl_vlan_setting vlan_strip;
struct iavf_cmd_info args;
uint32_t stripping_caps;
- uint32_t *vlan_setting;
+ uint32_t *ethertype;
int ret;
supported_caps = &vf->vlan_v2_caps.offloads.stripping_support;
if (supported_caps->outer) {
stripping_caps = supported_caps->outer;
- vlan_setting = &vlan_strip.outer_ethertype_setting;
+ ethertype = &vlan_strip.outer_ethertype_setting;
} else {
stripping_caps = supported_caps->inner;
- vlan_setting = &vlan_strip.inner_ethertype_setting;
+ ethertype = &vlan_strip.inner_ethertype_setting;
}
if (!(stripping_caps & VIRTCHNL_VLAN_ETHERTYPE_8100))
@@ -549,7 +549,7 @@ iavf_config_vlan_strip_v2(struct iavf_adapter *adapter, bool enable)
memset(&vlan_strip, 0, sizeof(vlan_strip));
vlan_strip.vport_id = vf->vsi_res->vsi_id;
- *vlan_setting = VIRTCHNL_VLAN_ETHERTYPE_8100;
+ *ethertype = VIRTCHNL_VLAN_ETHERTYPE_8100;
args.ops = enable ? VIRTCHNL_OP_ENABLE_VLAN_STRIPPING_V2 :
VIRTCHNL_OP_DISABLE_VLAN_STRIPPING_V2;
@@ -574,16 +574,16 @@ iavf_config_vlan_insert_v2(struct iavf_adapter *adapter, bool enable)
struct virtchnl_vlan_setting vlan_insert;
struct iavf_cmd_info args;
uint32_t insertion_caps;
- uint32_t *vlan_setting;
+ uint32_t *ethertype;
int ret;
supported_caps = &vf->vlan_v2_caps.offloads.insertion_support;
if (supported_caps->outer) {
insertion_caps = supported_caps->outer;
- vlan_setting = &vlan_insert.outer_ethertype_setting;
+ ethertype = &vlan_insert.outer_ethertype_setting;
} else {
insertion_caps = supported_caps->inner;
- vlan_setting = &vlan_insert.inner_ethertype_setting;
+ ethertype = &vlan_insert.inner_ethertype_setting;
}
if (!(insertion_caps & VIRTCHNL_VLAN_ETHERTYPE_8100))
@@ -591,7 +591,7 @@ iavf_config_vlan_insert_v2(struct iavf_adapter *adapter, bool enable)
memset(&vlan_insert, 0, sizeof(vlan_insert));
vlan_insert.vport_id = vf->vsi_res->vsi_id;
- *vlan_setting = VIRTCHNL_VLAN_ETHERTYPE_8100;
+ *ethertype = VIRTCHNL_VLAN_ETHERTYPE_8100;
args.ops = enable ? VIRTCHNL_OP_ENABLE_VLAN_INSERTION_V2 :
VIRTCHNL_OP_DISABLE_VLAN_INSERTION_V2;
--
2.30.0
next prev parent reply other threads:[~2021-01-20 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 1:10 [dpdk-dev] [PATCH v1] net/iavf: rename the VLAN offload virtchnl message Haiyue Wang
2021-01-20 3:15 ` [dpdk-dev] [PATCH v2] common/iavf: support VLAN filtering Haiyue Wang
2021-01-20 4:17 ` [dpdk-dev] [PATCH v3 0/2] iavf: update the VLAN offload message Haiyue Wang
2021-01-20 4:17 ` [dpdk-dev] [PATCH v3 1/2] common/iavf: support VLAN filtering Haiyue Wang
2021-01-20 6:34 ` Xing, Beilei
2021-01-20 4:17 ` Haiyue Wang [this message]
2021-01-20 6:35 ` [dpdk-dev] [PATCH v3 2/2] net/iavf: align to the new VLAN offload name Xing, Beilei
2021-01-20 5:46 ` [dpdk-dev] [PATCH v3 0/2] iavf: update the VLAN offload message Xing, Beilei
2021-01-20 10:16 ` Zhang, Qi Z
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=20210120041750.408535-3-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.fu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@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).