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 VNI of VXLAN encap action
Date: Mon, 19 Jun 2023 18:23:27 +0100 [thread overview]
Message-ID: <df484299-e1ae-73e0-1f1e-84cb0d5bd308@amd.com> (raw)
In-Reply-To: <20230613031539.30952-1-chaoyong.he@corigine.com>
On 6/13/2023 4:15 AM, Chaoyong He wrote:
> The 'vx_vni' field of VXLAN header is contain 24 bits of VNI and
> 8 bits of reserved. After convert into CPU endian, the reserved
> 8 bits should be shifted, or the VNI value will be not correct.
>
> Fixes: 861949032d0f ("net/nfp: fix VNI of VXLAN encap 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-06-19 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 3:15 Chaoyong He
2023-06-19 17:23 ` 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=df484299-e1ae-73e0-1f1e-84cb0d5bd308@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).