From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Wang, Jie1X" <jie1x.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yang, SteveX" <stevex.yang@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>
Subject: RE: [PATCH v2] net/ice/base: enable FDIR support for IPV6_NETX_PROTO
Date: Wed, 11 May 2022 15:04:13 +0000 [thread overview]
Message-ID: <8f3dcf1d9043436183358a00079bd85c@intel.com> (raw)
In-Reply-To: <2147216.ZfL8zNpBrT@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, May 11, 2022 10:55 PM
> To: Wang, Jie1X <jie1x.wang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Yang, SteveX <stevex.yang@intel.com>; Yang, Qiming
> <qiming.yang@intel.com>
> Subject: Re: [PATCH v2] net/ice/base: enable FDIR support for
> IPV6_NETX_PROTO
>
> 11/05/2022 16:31, Zhang, Qi Z:
> > From: Wang, Jie1X <jie1x.wang@intel.com>
> > >
> > > To support the new DDP and be compatible with the old version DDP
> > > file, API function 'check_ddp_support_proto_id' is added to detect
> > > if the required protocol ID is supported by the current DDP file.
> > >
> > > Add new protocol ID IPV6_NETX_PROTO support for PF FDIR if current
> > > DDP is new DDP and keep behavior if it is the old version DDP.
> > >
> > > v2: rebase and optimize the API function
> > >
> > > Signed-off-by: Jie Wang <jie1x.wang@intel.com>
> >
> > Acked-by: Qi Zhang <qi.z.zhang@intel.com>
> >
> > Applied to dpdk-next-net-intel.
>
> Do you mean NEXT_PROTO instead of NETX?
>
> Qi, I expect you fix this kind of mistake while merging please, thank you.
Yes, it should be NEXT_PROTO, I have fixed in dpdk-next-net-intel. thanks
>
prev parent reply other threads:[~2022-05-11 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 3:01 [PATCH] " Jie Wang
2022-05-07 9:13 ` [PATCH v2] " Jie Wang
2022-05-11 14:31 ` Zhang, Qi Z
2022-05-11 14:55 ` Thomas Monjalon
2022-05-11 15:04 ` Zhang, Qi Z [this message]
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=8f3dcf1d9043436183358a00079bd85c@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jie1x.wang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stevex.yang@intel.com \
--cc=thomas@monjalon.net \
/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).