From: Gregory Etelson <getelson@nvidia.com>
To: <dev@dpdk.org>
Cc: <getelson@nvidia.com>, <mkashani@nvidia.com>,
<rasland@nvidia.com>, "Ori Kam" <orika@nvidia.com>
Subject: [PATCH 0/2] fix IP-in-IP tunnels recognition
Date: Thu, 29 Feb 2024 18:05:02 +0200 [thread overview]
Message-ID: <20240229160505.630586-1-getelson@nvidia.com> (raw)
fix IP-in-IP tunnels validation and recognition
Gregory Etelson (2):
net/mlx5: remove code duplications
net/mlx5: fix IP-in-IP tunnels recognition
drivers/net/mlx5/mlx5_flow_dv.c | 243 +++++++++++++++-----------------
1 file changed, 117 insertions(+), 126 deletions(-)
Acked-by: Ori Kam <orika@nvidia.com>
--
2.39.2
next reply other threads:[~2024-02-29 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 16:05 Gregory Etelson [this message]
2024-02-29 16:05 ` [PATCH 1/2] net/mlx5: remove code duplications Gregory Etelson
2024-02-29 16:05 ` [PATCH 2/2] net/mlx5: fix IP-in-IP tunnels recognition Gregory Etelson
2024-03-13 7:39 ` Raslan Darawsheh
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=20240229160505.630586-1-getelson@nvidia.com \
--to=getelson@nvidia.com \
--cc=dev@dpdk.org \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.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).