From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Yahui Cao <yahui.cao@intel.com>
Cc: Qiming Yang <qiming.yang@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
dev@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/ice: remove GTPU tunnel support for inner L4
Date: Thu, 31 Oct 2019 10:54:28 +0800 [thread overview]
Message-ID: <20191031025428.GL11315@intel.com> (raw)
In-Reply-To: <20191031103817.70867-1-yahui.cao@intel.com>
Hi, yahui
Prefer to give more details like why we need this patch in commit log.
Thanks,
Xiaolong
On 10/31, Yahui Cao wrote:
>Fixes: efc16c621415 ("net/ice: support flow director GTPU tunnel")
>
>Signed-off-by: Yahui Cao <yahui.cao@intel.com>
>---
> drivers/net/ice/ice_fdir_filter.c | 4 ----
> 1 file changed, 4 deletions(-)
>
>diff --git a/drivers/net/ice/ice_fdir_filter.c b/drivers/net/ice/ice_fdir_filter.c
>index 736ccd54e..d80dafa20 100644
>--- a/drivers/net/ice/ice_fdir_filter.c
>+++ b/drivers/net/ice/ice_fdir_filter.c
>@@ -128,10 +128,6 @@ static struct ice_pattern_match_item ice_fdir_pattern_comms[] = {
> {pattern_eth_ipv4_udp_vxlan_eth_ipv4_sctp,
> ICE_FDIR_INSET_VXLAN_IPV4_SCTP, ICE_INSET_NONE},
> {pattern_eth_ipv4_gtpu_ipv4, ICE_FDIR_INSET_GTPU_IPV4, ICE_INSET_NONE},
>- {pattern_eth_ipv4_gtpu_ipv4_tcp,
>- ICE_FDIR_INSET_GTPU_IPV4, ICE_INSET_NONE},
>- {pattern_eth_ipv4_gtpu_ipv4_udp,
>- ICE_FDIR_INSET_GTPU_IPV4, ICE_INSET_NONE},
> };
>
> static struct ice_flow_parser ice_fdir_parser_os;
>--
>2.17.1
>
next prev parent reply other threads:[~2019-10-31 2:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 10:38 [dpdk-dev] [PATCH] net/ice: remove GTPU tunnel support for inner L4 Yahui Cao
2019-10-31 2:54 ` Ye Xiaolong [this message]
2019-10-31 11:22 ` [dpdk-dev] [PATCH v2] " Yahui Cao
2019-10-31 13:05 ` [dpdk-dev] [PATCH v3] " Yahui Cao
2019-11-01 2:13 ` Ye Xiaolong
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=20191031025428.GL11315@intel.com \
--to=xiaolong.ye@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=yahui.cao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.