From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, dev@dpdk.org
Cc: matan@nvidia.com, rasland@nvidia.com, orika@nvidia.com,
dsosnowski@nvidia.com
Subject: Re: [PATCH v3 1/6] ethdev: add modify IPv4 next protocol field
Date: Mon, 12 Feb 2024 17:17:03 +0000 [thread overview]
Message-ID: <9e487beb-d47b-4b67-b597-96050ddfb70e@amd.com> (raw)
In-Reply-To: <20240207122908.20646-1-viacheslavo@nvidia.com>
On 2/7/2024 12:29 PM, Viacheslav Ovsiienko wrote:
> Add IPv4 next protocol modify field definition.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
next prev parent reply other threads:[~2024-02-12 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 12:29 Viacheslav Ovsiienko
2024-02-07 12:29 ` [PATCH v3 2/6] app/testpmd: add modify IPv4 next protocol command line Viacheslav Ovsiienko
2024-02-12 17:17 ` Ferruh Yigit
2024-02-07 12:29 ` [PATCH v3 3/6] net/mlx5: add modify IPv4 protocol implementation Viacheslav Ovsiienko
2024-02-07 12:29 ` [PATCH v3 4/6] ethdev: add modify action support for IPsec fields Viacheslav Ovsiienko
2024-02-08 16:07 ` Ori Kam
2024-02-12 17:17 ` Ferruh Yigit
2024-02-07 12:29 ` [PATCH v3 5/6] app/testpmd: add modify ESP related fields command line Viacheslav Ovsiienko
2024-02-12 17:17 ` Ferruh Yigit
2024-02-07 12:29 ` [PATCH v3 6/6] net/mlx5: add modify field action IPsec support Viacheslav Ovsiienko
2024-02-12 17:17 ` Ferruh Yigit [this message]
2024-02-14 4:04 ` [PATCH v3 1/6] ethdev: add modify IPv4 next protocol field 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=9e487beb-d47b-4b67-b597-96050ddfb70e@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@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).