From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Ferruh Yigit'" <ferruh.yigit@intel.com>,
"'Rasesh Mody'" <rmody@marvell.com>,
"'Shahed Shaikh'" <shshaikh@marvell.com>,
"'Rahul Lakkireddy'" <rahul.lakkireddy@chelsio.com>,
"'Qi Zhang'" <qi.z.zhang@intel.com>,
"'Xiao Wang'" <xiao.w.wang@intel.com>,
"'Ziyang Xuan'" <xuanziyang2@huawei.com>,
"'Xiaoyun Wang'" <cloud.wangxiaoyun@huawei.com>,
"'Guoyang Zhou'" <zhouguoyang@huawei.com>,
"'Beilei Xing'" <beilei.xing@intel.com>,
"'Jingjing Wu'" <jingjing.wu@intel.com>,
"'Qiming Yang'" <qiming.yang@intel.com>,
"'Rosen Xu'" <rosen.xu@intel.com>,
"'Haiyue Wang'" <haiyue.wang@intel.com>,
"'Jian Wang'" <jianwang@trustnetic.com>,
"'Maxime Coquelin'" <maxime.coquelin@redhat.com>,
"'Chenbo Xia'" <chenbo.xia@intel.com>,
"'Olivier Matz'" <olivier.matz@6wind.com>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH] net: add macro for VLAN header length
Date: Fri, 12 Nov 2021 14:09:08 +0800 [thread overview]
Message-ID: <002c01d7d78b$cf72c430$6e584c90$@trustnetic.com> (raw)
In-Reply-To: <20211110174029.614449-1-ferruh.yigit@intel.com>
On November 11, 2021 1:40 AM, Ferruh Yigit wrote:
> Multiple drivers are defining macros for VLAN header length, to remove the
> redundancy defining macro in the ether header.
> And updated drivers to use the new macro.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> drivers/net/bnx2x/bnx2x_vfpf.c | 2 +-
> drivers/net/bnx2x/bnx2x_vfpf.h | 2 --
> drivers/net/cxgbe/cxgbe_compat.h | 1 -
> drivers/net/cxgbe/sge.c | 2 +-
> drivers/net/fm10k/fm10k.h | 2 --
> drivers/net/fm10k/fm10k_ethdev.c | 2 +-
> drivers/net/hinic/hinic_pmd_ethdev.h | 3 +--
> drivers/net/i40e/i40e_ethdev.h | 4 +---
> drivers/net/iavf/iavf.h | 3 +--
> drivers/net/ice/ice_dcf_ethdev.c | 2 +-
> drivers/net/ice/ice_ethdev.h | 4 +---
> drivers/net/ipn3ke/ipn3ke_ethdev.h | 3 +--
> drivers/net/ixgbe/ixgbe_ethdev.c | 4 ++--
> drivers/net/ixgbe/ixgbe_ethdev.h | 1 -
> drivers/net/ixgbe/ixgbe_rxtx.c | 4 ++--
> drivers/net/ngbe/ngbe_ethdev.c | 2 +-
> drivers/net/ngbe/ngbe_ethdev.h | 1 -
> drivers/net/ngbe/ngbe_rxtx.c | 2 +-
> drivers/net/txgbe/txgbe_ethdev.c | 2 +-
> drivers/net/txgbe/txgbe_ethdev.h | 1 -
> drivers/net/txgbe/txgbe_ethdev_vf.c | 2 +-
> drivers/net/txgbe/txgbe_rxtx.c | 4 ++--
For txgbe/ngbe,
Acked-by: Jiawen Wu <jiawenwu@trustnetic.com>
> examples/vhost/main.c | 3 +--
> lib/net/rte_ether.h | 5 +++--
> 24 files changed, 23 insertions(+), 38 deletions(-)
next prev parent reply other threads:[~2021-11-12 6:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 17:40 Ferruh Yigit
2021-11-11 1:34 ` Wang, Haiyue
2021-11-12 2:36 ` Xu, Rosen
2021-11-12 6:09 ` Jiawen Wu [this message]
2021-11-16 23:14 ` Thomas Monjalon
2021-11-17 10:00 ` Ferruh Yigit
2021-11-17 10:02 ` Thomas Monjalon
2021-11-17 10:12 ` Ferruh Yigit
2021-11-17 18:08 ` [PATCH v2] " Ferruh Yigit
2021-11-17 18:24 ` [PATCH v3] " Ferruh Yigit
2021-11-17 18:54 ` Thomas Monjalon
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='002c01d7d78b$cf72c430$6e584c90$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=beilei.xing@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=jianwang@trustnetic.com \
--cc=jingjing.wu@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rmody@marvell.com \
--cc=rosen.xu@intel.com \
--cc=shshaikh@marvell.com \
--cc=xiao.w.wang@intel.com \
--cc=xuanziyang2@huawei.com \
--cc=zhouguoyang@huawei.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).