From: "Huang, ZhiminX" <zhiminx.huang@intel.com>
To: "Wu, WenxuanX" <wenxuanx.wu@intel.com>,
"qiz.zhang@intel.com" <qiz.zhang@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"Wu, WenxuanX" <wenxuanx.wu@intel.com>,
"Su, Simei" <simei.su@intel.com>,
"stable@dpdk.com" <stable@dpdk.com>
Subject: RE: [PATCH v2] net/iavf: fix gtpu extension flow error
Date: Thu, 7 Jul 2022 06:11:23 +0000 [thread overview]
Message-ID: <BN0PR11MB57121024845A77C70F612AEEFD839@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220706025626.1070737-1-wenxuanx.wu@intel.com>
> -----Original Message-----
> From: wenxuanx.wu@intel.com <wenxuanx.wu@intel.com>
> Sent: Wednesday, July 6, 2022 10:56 AM
> To: qiz.zhang@intel.com; Xing, Beilei <beilei.xing@intel.com>; dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Zhou, YidingX
> <yidingx.zhou@intel.com>; Wu, WenxuanX <wenxuanx.wu@intel.com>; Su,
> Simei <simei.su@intel.com>; stable@dpdk.com
> Subject: [PATCH v2] net/iavf: fix gtpu extension flow error
>
> From: Wenxuan Wu <wenxuanx.wu@intel.com>
>
> Due to the change of struct rte_gtp_psc_generic_hdr, kernel driver can not
> handle gtp_psc properly, we introduce a new structure to fix this gap between
> kernel driver and struct rte_gtp_psc_generic_hdr.
>
> Fixes: d5eb3e600d9e ("net/iavf: support flow director basic rule")
> Cc: simei.su@intel.com
> Cc: stable@dpdk.com
>
> Signed-off-by: Wenxuan Wu <wenxuanx.wu@intel.com>
>
Tested-by: Zhimin Huang <zhiminx.huang@intel.com >
next prev parent reply other threads:[~2022-07-07 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 10:09 [PATCH] " wenxuanx.wu
2022-07-05 11:52 ` Zhang, Qi Z
2022-07-06 2:56 ` [PATCH v2] " wenxuanx.wu
2022-07-07 6:11 ` Huang, ZhiminX [this message]
2022-07-07 6:57 ` Yang, Qiming
2022-07-07 7:13 ` Zhang, Qi Z
2022-07-11 15:18 ` Thomas Monjalon
2022-07-06 2:45 wenxuanx.wu
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=BN0PR11MB57121024845A77C70F612AEEFD839@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=zhiminx.huang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.com \
--cc=qiz.zhang@intel.com \
--cc=simei.su@intel.com \
--cc=stable@dpdk.com \
--cc=wenxuanx.wu@intel.com \
--cc=yidingx.zhou@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).