From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Maayan Kashani <mkashani@nvidia.com>, Ori Kam <orika@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Yongseok Koh <yskoh@mellanox.com>
Subject: RE: [PATCH 2/2] net/mlx5: fix IP-in-IP tunnels recognition
Date: Wed, 13 Mar 2024 07:39:27 +0000 [thread overview]
Message-ID: <MN0PR12MB6056B8819B431F56F1CCCFDDCF2A2@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240229160505.630586-3-getelson@nvidia.com>
Hi,
> -----Original Message-----
> From: Gregory Etelson <getelson@nvidia.com>
> Sent: Thursday, February 29, 2024 6:05 PM
> To: dev@dpdk.org
> Cc: Gregory Etelson <getelson@nvidia.com>; Maayan Kashani
> <mkashani@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>; Ori Kam
> <orika@nvidia.com>; Dariusz Sosnowski <dsosnowski@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>; Matan Azrad <matan@nvidia.com>; Yongseok
> Koh <yskoh@mellanox.com>
> Subject: [PATCH 2/2] net/mlx5: fix IP-in-IP tunnels recognition
>
> The patch fixes IP-in-IP tunnel recognition for the following patterns
>
> / [ipv4|ipv6] proto is [ipv4|ipv6] / end
>
> / [ipv4|ipv6] / [ipv4|ipv6] /
>
> Fixes: 3d69434113d1 ("net/mlx5: add Direct Verbs validation function")
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2024-03-13 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 16:05 [PATCH 0/2] " Gregory Etelson
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 [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=MN0PR12MB6056B8819B431F56F1CCCFDDCF2A2@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=yskoh@mellanox.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).