From: Akhil Goyal <gakhil@marvell.com>
To: Brian Dooley <brian.dooley@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>, Kai Ji <kai.ji@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: RE: [EXT] [PATCH v5] examples/fips_validation: add parsing for AES CTR
Date: Mon, 10 Oct 2022 19:49:49 +0000 [thread overview]
Message-ID: <CO6PR18MB44847E63B5999CFE35E435DED8209@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221007165829.732961-1-brian.dooley@intel.com>
> Added functionality to parse algorithm for AES CTR test
>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> Acked-by: Kai Ji <kai.ji@intel.com>
> Acked-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> ---
> v2: fix clang warning for int-in-bool-context
> ---
> v3: in reply to fix and patchwork CI
> ---
> v4: missing acks
> ---
> v5: add documentation
> ---
> doc/guides/sample_app_ug/fips_validation.rst | 2 ++
> examples/fips_validation/fips_validation.c | 2 ++
> examples/fips_validation/fips_validation.h | 2 ++
> examples/fips_validation/fips_validation_aes.c | 5 +++++
> examples/fips_validation/main.c | 9 +++++++--
> 5 files changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/sample_app_ug/fips_validation.rst
> b/doc/guides/sample_app_ug/fips_validation.rst
> index 6f4bd34726..6e5885e23b 100644
> --- a/doc/guides/sample_app_ug/fips_validation.rst
> +++ b/doc/guides/sample_app_ug/fips_validation.rst
> @@ -61,6 +61,8 @@ ACVP
> * AES-CBC (128,192,256) - AFT, MCT
> * AES-GCM (128,192,256) - AFT
> * AES-CMAC (128,192,256) - AFT
> + * AES-CTR (128,192,256) - AFT, CTR
> + * AES-GMAC (128,192,256) - AFT
Removed GMAC from this patch and added in GMAC FIPS support
Applied to dpdk-next-crypto
Thanks
prev parent reply other threads:[~2022-10-10 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220930085302.317536-1-brian.dooley@intel.com>
2022-10-07 16:58 ` Brian Dooley
2022-10-10 19:49 ` 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=CO6PR18MB44847E63B5999CFE35E435DED8209@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gmuthukrishn@marvell.com \
--cc=kai.ji@intel.com \
--cc=stable@dpdk.org \
/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).