From: Akhil Goyal <gakhil@marvell.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
Vidya Sagar Velumuri <vvelumuri@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] test/crypto: fix: test vectors for zuc 256 bit key
Date: Thu, 4 Nov 2021 18:38:21 +0000 [thread overview]
Message-ID: <CO6PR18MB44840D8EF6665B162CF0E293D88D9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <DM8PR11MB5591D94D170FA8B1DA4CD70E848D9@DM8PR11MB5591.namprd11.prod.outlook.com>
> > > Subject: [PATCH v3] test/crypto: fix: test vectors for zuc 256 bit key
> > >
> > > Fix the test vectors added for zuc 256-bit key Add known vectors form
> > > ZUC 256 RFC.
> > >
> > > Fixes: fa5bf9345d4e (test/crypto: add ZUC cases with 256-bit keys)
> > >
> > > Signed-off-by: Vidya Sagar Velumuri <vvelumuri@marvell.com>
> >
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2021-11-04 18:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 8:40 [dpdk-dev] [PATCH v1] " Vidya Sagar Velumuri
2021-10-28 7:10 ` Akhil Goyal
2021-10-29 12:37 ` De Lara Guarch, Pablo
2021-10-30 12:25 ` Vidya Sagar Velumuri
2021-10-31 22:06 ` De Lara Guarch, Pablo
2021-11-01 10:23 ` Vidya Sagar Velumuri
2021-11-02 4:40 ` Vidya Sagar Velumuri
2021-11-02 11:17 ` De Lara Guarch, Pablo
2021-11-03 6:55 ` [dpdk-dev] [PATCH v2] " Vidya Sagar Velumuri
2021-11-03 9:28 ` De Lara Guarch, Pablo
2021-11-03 9:31 ` [dpdk-dev] [PATCH v3] " Vidya Sagar Velumuri
2021-11-04 10:52 ` Akhil Goyal
2021-11-04 12:18 ` De Lara Guarch, Pablo
2021-11-04 18:38 ` Akhil Goyal [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=CO6PR18MB44840D8EF6665B162CF0E293D88D9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=ktejasree@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@intel.com \
--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).