From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Sunyang Wu <sunyang.wu@jaguarmicro.com>, dev@dpdk.org
Cc: david.marchand@redhat.com, orika@nvidia.com, stable@dpdk.org,
Joey Xing <joey.xing@jaguarmicro.com>
Subject: Re: [PATCH v2] lib/ethdev: modified the definition of 'NVGRE_ENCAP'
Date: Thu, 30 Nov 2023 10:35:47 +0000 [thread overview]
Message-ID: <4dc15c5d-03a0-4748-b11c-6ba90c0a37ab@amd.com> (raw)
In-Reply-To: <20231130062221.43876-1-sunyang.wu@jaguarmicro.com>
On 11/30/2023 6:22 AM, Sunyang Wu wrote:
> Fix the issue of incorrect definition of 'NVGRE_ENCAP', and
> modified the error comments of 'rte_flow_action_nvgre_encap'.
>
> Fixes: c2beb1d469d2 ("ethdev: add missing items/actions to flow object
> converter")
> Fixes: 3850cf0c8c37 ("ethdev: add tunnel encap/decap actions")
> Cc: stable@dpdk.org
>
> Signed-off-by: Joey Xing <joey.xing@jaguarmicro.com>
> Signed-off-by: Sunyang Wu <sunyang.wu@jaguarmicro.com>
>
Moving from previous version:
Acked-by: Ori Kam <orika@nvidia.com>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-11-30 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 6:22 Sunyang Wu
2023-11-30 10:35 ` Ferruh Yigit [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=4dc15c5d-03a0-4748-b11c-6ba90c0a37ab@amd.com \
--to=ferruh.yigit@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=joey.xing@jaguarmicro.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=sunyang.wu@jaguarmicro.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).