From: Kevin Traynor <ktraynor@redhat.com>
To: Ankur Dwivedi <adwivedi@marvell.com>, stable@dpdk.org
Cc: anoobj@marvell.com, gakhil@marvell.com, ktejasree@marvell.com,
jerinj@marvell.com, vvelumuri@marvell.com
Subject: Re: [PATCH 21.11 1/2] common/cnxk: swap zuc-256 key
Date: Fri, 24 Jun 2022 14:20:04 +0100 [thread overview]
Message-ID: <40080e7a-5589-b304-51eb-740723004657@redhat.com> (raw)
In-Reply-To: <20220624071809.27393-2-adwivedi@marvell.com>
On 24/06/2022 08:18, Ankur Dwivedi wrote:
> [ upstream commit 5242d8dbbed7fa78c01e86777a4cbc96f5605372 ]
>
> The microcode expects zuc-256 key to be in reverse of what is
> provided by dpdk test app. This patch swaps the zuc-256 key.
>
> Fixes: 66a8a26f311f ("common/cnxk: fix ZUC constants")
>
> Signed-off-by: Ankur Dwivedi<adwivedi@marvell.com>
Thanks for resending Ankur. I have queued these patches for the 21.11
branch. They will be pushed to dpdk.org in a few days time.
next prev parent reply other threads:[~2022-06-24 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 7:18 [PATCH 21.11 0/2] fix zuc-256 cipher support Ankur Dwivedi
2022-06-24 7:18 ` [PATCH 21.11 1/2] common/cnxk: swap zuc-256 key Ankur Dwivedi
2022-06-24 13:20 ` Kevin Traynor [this message]
2022-06-24 7:18 ` [PATCH 21.11 2/2] crypto/cnxk: swap zuc-256 iv Ankur Dwivedi
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=40080e7a-5589-b304-51eb-740723004657@redhat.com \
--to=ktraynor@redhat.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.com \
--cc=stable@dpdk.org \
--cc=vvelumuri@marvell.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).