DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Power, Ciara" <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH v2 0/5] test/crypto: add ZUC256 chained tests
Date: Tue, 14 Mar 2023 10:27:32 +0000	[thread overview]
Message-ID: <CO6PR18MB44846C20F3A70EA5CD392E7BD8BE9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <DM8PR11MB5591A93602D27DD668BDCA8484B69@DM8PR11MB5591.namprd11.prod.outlook.com>

> > Subject: [PATCH v2 0/5] test/crypto: add ZUC256 chained tests
> >
> > This patchset adds chained testcases for each ZUC256 digest size:
> >  - cipher-auth
> >  - auth-cipher
> >  - auth-cipher-verify
> >
> >  To add these tests, some improvements were made to the existing code,
> > allowing for the user to easily differentiate ZUC256 and ZUC128 tests.
> >
> >  Some fixes are also included, that were highlighted when these new tests
> > were added.
> >
> >  v2: changed bit lengths to byte length representation.
> >
> > Ciara Power (5):
> >   test/crypto: improve readability of ZUC256 tests
> >   test/crypto: fix ZUC digest length in comparison
> >   test/crypto: fix auth op parameter for ZUC256 tests
> >   test/crypto: fix capability check for ZUC cipher auth
> >   test/crypto: add chained ZUC256 testcases
> >
> >  app/test/test_cryptodev.c                  | 280 +++++---
> >  app/test/test_cryptodev_zuc_test_vectors.h | 714 +++++++++++++++++++++
> >  2 files changed, 913 insertions(+), 81 deletions(-)
> >
> > --
> > 2.25.1
> 
> Series-acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2023-03-14 10:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 16:39 [PATCH " Ciara Power
2023-03-01 16:39 ` [PATCH 1/5] test/crypto: improve readability of ZUC256 tests Ciara Power
2023-03-01 16:39 ` [PATCH 2/5] test/crypto: fix ZUC digest length in comparison Ciara Power
2023-03-01 16:39 ` [PATCH 3/5] test/crypto: fix auth op parameter for ZUC256 tests Ciara Power
2023-03-01 16:39 ` [PATCH 4/5] test/crypto: fix capability check for ZUC cipher auth Ciara Power
2023-03-01 16:39 ` [PATCH 5/5] test/crypto: add chained ZUC256 testcases Ciara Power
2023-03-02  9:56   ` De Lara Guarch, Pablo
2023-03-02 10:07 ` [PATCH 0/5] test/crypto: add ZUC256 chained tests Dooley, Brian
2023-03-03  9:38 ` [PATCH v2 " Ciara Power
2023-03-03  9:38   ` [PATCH v2 1/5] test/crypto: improve readability of ZUC256 tests Ciara Power
2023-03-03  9:38   ` [PATCH v2 2/5] test/crypto: fix ZUC digest length in comparison Ciara Power
2023-03-03  9:38   ` [PATCH v2 3/5] test/crypto: fix auth op parameter for ZUC256 tests Ciara Power
2023-03-03  9:38   ` [PATCH v2 4/5] test/crypto: fix capability check for ZUC cipher auth Ciara Power
2023-03-03  9:38   ` [PATCH v2 5/5] test/crypto: add chained ZUC256 testcases Ciara Power
2023-03-03 16:37   ` [EXT] [PATCH v2 0/5] test/crypto: add ZUC256 chained tests Tejasree Kondoj
2023-03-06  9:32   ` De Lara Guarch, Pablo
2023-03-14 10:27     ` 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=CO6PR18MB44846C20F3A70EA5CD392E7BD8BE9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@intel.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).