From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 1/2] test/crypto: use separate keys for auth and cipher
Date: Wed, 24 May 2023 12:26:52 +0000 [thread overview]
Message-ID: <CO6PR18MB4484BECA3FAAD6BBCB1D73C2D8419@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN7PR11MB763974BE8027EAE836277BDEE67E9@SN7PR11MB7639.namprd11.prod.outlook.com>
> > Subject: [PATCH 1/2] test/crypto: use separate keys for auth and cipher
> >
> > The mixed test cases can have keys with different key lengths. The routine
> > which prepares the session parameters uses same key length for both cipher
> > & auth keys. Instead allow the caller to use same keys as required.
> >
> > Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> > ---
> > app/test/test_cryptodev.c | 48 +++++++++++++++++++++++----------------
> > 1 file changed, 28 insertions(+), 20 deletions(-)
>
> Acked-by: Ciara Power <ciara.power@intel.com>
Patchset applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2023-05-24 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 5:33 Anoob Joseph
2023-05-12 5:33 ` [PATCH 2/2] test/crypto: specify correct parameters with null algos Anoob Joseph
2023-05-16 10:22 ` Akhil Goyal
2023-05-17 15:50 ` Power, Ciara
2023-05-16 10:22 ` [PATCH 1/2] test/crypto: use separate keys for auth and cipher Akhil Goyal
2023-05-17 15:41 ` Power, Ciara
2023-05-24 12:26 ` 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=CO6PR18MB4484BECA3FAAD6BBCB1D73C2D8419@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@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).