From: "Power, Ciara" <ciara.power@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>, "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH v4 0/3] Replace obsolote test cases.
Date: Mon, 26 Jun 2023 12:56:22 +0000 [thread overview]
Message-ID: <SN7PR11MB7639474751CCE7D92B83A9D5E626A@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230620103235.539282-1-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Tuesday 20 June 2023 11:33
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; Power, Ciara
> <ciara.power@intel.com>; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v4 0/3] Replace obsolote test cases.
>
> This patchset removes obsolete test cases for RSA, MOD EXP, MOD INV.
> Doing that, new way of handling ut_setup and ut_teardown was proposed.
> Now both behave like constructor/desctuctor in the unit tests.
> It frees particular alghorithm functions from any kind of responsibility to free
> resources for the new functions.
>
> v2:
> - fixed build problem with non compile-time constant
> v3:
> - rebased
> - left old pwct tests intact
> v4:
> - fixed mailmap mismatch
> - rebased
>
> Arkadiusz Kusztal (3):
> app/test: remove obsolete test function
> app/test: add modexp and modinv functions
> app/test: add rsa none padding tests
>
> app/test/test_cryptodev_asym.c | 775 +++++++++-----------
> app/test/test_cryptodev_mod_test_vectors.h | 814 +--------------------
> app/test/test_cryptodev_rsa_test_vectors.h | 322 ++++----
> 3 files changed, 510 insertions(+), 1401 deletions(-)
>
> --
> 2.25.1
Series-acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2023-06-26 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:32 Arkadiusz Kusztal
2023-06-20 10:32 ` [PATCH v4 1/3] app/test: remove obsolete test function Arkadiusz Kusztal
2023-06-20 10:32 ` [PATCH v4 2/3] app/test: add modexp and modinv functions Arkadiusz Kusztal
2023-06-20 10:32 ` [PATCH v4 3/3] app/test: add rsa none padding tests Arkadiusz Kusztal
2023-06-26 12:56 ` Power, Ciara [this message]
2023-07-03 11:35 ` [EXT] [PATCH v4 0/3] Replace obsolote test cases Gowrishankar Muthukrishnan
2023-07-03 14:14 ` Akhil Goyal
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=SN7PR11MB7639474751CCE7D92B83A9D5E626A@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@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).