From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com, stable@dpdk.org
Subject: Re: [PATCH] net/nfp: fix the incorrect vni of VXLAN encap action
Date: Wed, 15 Feb 2023 14:01:32 +0000 [thread overview]
Message-ID: <6f368389-3499-f920-c490-22f6eeb5ba8c@amd.com> (raw)
In-Reply-To: <20230208092350.26226-1-chaoyong.he@corigine.com>
On 2/8/2023 9:23 AM, Chaoyong He wrote:
> The helper function which send the tunnel configuration to
> firmware requires the vni with CPU endian.
> The original VXLAN encap logic wrongly invoke it with the
> big-endian value.
>
> Fixes: 724662b4ce5b ("net/nfp: support IPv4 VXLAN encap flow action")
> Fixes: c3b7254093c2 ("net/nfp: support IPv6 VXLAN encap flow action")
> Cc: stable@dpdk.org
>
> Signed-off-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-02-15 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 9:23 Chaoyong He
2023-02-15 14:01 ` 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=6f368389-3499-f920-c490-22f6eeb5ba8c@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=stable@dpdk.org \
/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).