From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Michael Baum <michaelba@nvidia.com>, dev@dpdk.org
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>, Ori Kam <orika@nvidia.com>,
stable@dpdk.org
Subject: Re: [PATCH] ethdev: fix GENEVE option item conversion
Date: Fri, 19 Jul 2024 09:31:48 +0100 [thread overview]
Message-ID: <34ac2eda-6e01-49fc-9832-6ea1bc2c621f@amd.com> (raw)
In-Reply-To: <20240715121316.3429593-1-michaelba@nvidia.com>
On 7/15/2024 1:13 PM, Michael Baum wrote:
> The "rte_flow_conv()" function, enables, among other things, to copy
> item list.
>
> For GENEVE option item, the function copies it without considering deep
> copy. It copies the "data" pointer without copying the pointed values.
>
> This patch adds deep copy for after regular copy.
>
> Fixes: 2b4c72b4d10d ("ethdev: introduce GENEVE header TLV option item")
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-07-19 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 12:13 Michael Baum
2024-07-19 8:31 ` 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=34ac2eda-6e01-49fc-9832-6ea1bc2c621f@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).