From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>
Cc: Fan Zhang <roy.fan.zhang@intel.com>,
Brian Dooley <brian.dooley@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
"Archana Muniganti" <marchana@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: [PATCH v3 0/3] example/fips_validation: add xts and sha json parsing
Date: Wed, 29 Jun 2022 15:22:29 +0530 [thread overview]
Message-ID: <cover.1656495592.git.gmuthukrishn@marvell.com> (raw)
In-Reply-To: <f5e27077cb6893c157f932d082ce62173111530f.1656421415.git.gmuthukrishn@marvell.com>
Add support in fips_validation to parse AES_XTS and SHA json vectors.
v3:
- individual patches for xts and sha are clubbed in this new series.
Gowrishankar Muthukrishnan (3):
examples/fips_validation: add aes_cbc specific enum
examples/fips_validation: add parsing for xts
examples/fips_validation: add parsing for sha
examples/fips_validation/fips_validation.c | 6 +-
examples/fips_validation/fips_validation.h | 26 ++-
.../fips_validation/fips_validation_sha.c | 188 ++++++++++++++++++
.../fips_validation/fips_validation_xts.c | 141 +++++++++++++
examples/fips_validation/main.c | 44 +++-
5 files changed, 392 insertions(+), 13 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2022-06-29 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 7:58 [PATCH v1] examples/fips_validation: add parsing for xts Gowrishankar Muthukrishnan
2022-06-28 11:57 ` David Marchand
2022-06-29 9:14 ` [EXT] " Gowrishankar Muthukrishnan
2022-06-28 13:12 ` [PATCH v2] " Gowrishankar Muthukrishnan
2022-06-29 8:07 ` Zhang, Roy Fan
2022-06-29 9:52 ` Gowrishankar Muthukrishnan [this message]
2022-06-29 9:52 ` [PATCH v3 1/3] examples/fips_validation: add aes_cbc specific enum Gowrishankar Muthukrishnan
2022-06-29 9:52 ` [PATCH v3 2/3] examples/fips_validation: add parsing for xts Gowrishankar Muthukrishnan
2022-06-29 9:52 ` [PATCH v3 3/3] examples/fips_validation: add parsing for sha Gowrishankar Muthukrishnan
2022-06-29 12:35 ` [PATCH v4 0/3] example/fips_validation: add xts and sha json parsing Gowrishankar Muthukrishnan
2022-06-29 12:35 ` [PATCH v4 1/3] examples/fips_validation: add aes_cbc specific enum Gowrishankar Muthukrishnan
2022-06-29 12:35 ` [PATCH v4 2/3] examples/fips_validation: add parsing for xts Gowrishankar Muthukrishnan
2022-06-29 12:35 ` [PATCH v4 3/3] examples/fips_validation: add parsing for sha Gowrishankar Muthukrishnan
2022-06-30 4:22 ` [EXT] [PATCH v4 0/3] example/fips_validation: add xts and sha json parsing 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=cover.1656495592.git.gmuthukrishn@marvell.com \
--to=gmuthukrishn@marvell.com \
--cc=anoobj@marvell.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=marchana@marvell.com \
--cc=roy.fan.zhang@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).