From: Thomas Monjalon <thomas@monjalon.net>
To: "Yang, Qiming" <qiming.yang@intel.com>,
"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: "Zhou, YidingX" <yidingx.zhou@intel.com>,
"Su, Simei" <simei.su@intel.com>,
"stable@dpdk.com" <stable@dpdk.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [PATCH v2] net/iavf: fix gtpu extension flow error
Date: Mon, 11 Jul 2022 17:18:40 +0200 [thread overview]
Message-ID: <3415984.dkkaz22YKf@thomas> (raw)
In-Reply-To: <DM4PR11MB599476F440DB6F0E1656CD13D7839@DM4PR11MB5994.namprd11.prod.outlook.com>
07/07/2022 09:13, Zhang, Qi Z:
> From: Yang, Qiming <qiming.yang@intel.com>
> > From: Wu, WenxuanX <wenxuanx.wu@intel.com>
> > > 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
> >
> > This line should be delete before patch sent.
> >
> > > Cc: stable@dpdk.com
it is dpdk.org!
> > >
> > > Signed-off-by: Wenxuan Wu <wenxuanx.wu@intel.com>
> >
> > Acked-by: Qiming Yang <Qiming.yang@intel.com>
no uppercase or double space in emails please
>
> Applied to dpdk-next-net-intel.
>
> Thanks
> Qi
next prev parent reply other threads:[~2022-07-11 15:18 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
2022-07-07 6:57 ` Yang, Qiming
2022-07-07 7:13 ` Zhang, Qi Z
2022-07-11 15:18 ` Thomas Monjalon [this message]
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=3415984.dkkaz22YKf@thomas \
--to=thomas@monjalon.net \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--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).