From: Akhil Goyal <gakhil@marvell.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: RE: [PATCH v2 2/2] examples/fips_validation: add parsing for TDES
Date: Fri, 7 Oct 2022 09:55:06 +0000 [thread overview]
Message-ID: <CO6PR18MB448411DFFB637D271B6C7F35D85F9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CY4PR11MB18488D0703BC5EA04E78E74083519@CY4PR11MB1848.namprd11.prod.outlook.com>
> > Subject: [PATCH v2 2/2] examples/fips_validation: add parsing for TDES
> >
> > Added function to parse algorithm for TDES CBC and ECB tests in json.
> >
> > Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> > ---
>
> Acked-by: Brian Dooley <brian.dooley@intel.com>
Series applied to dpdk-next-crypto
Thanks.
next prev parent reply other threads:[~2022-10-07 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 6:39 [PATCH v1 1/2] examples/fips_validation: skip offsetting source for json vectors Gowrishankar Muthukrishnan
2022-07-13 6:39 ` [PATCH v1 2/2] examples/fips_validation: add parsing for tdes Gowrishankar Muthukrishnan
2022-08-12 11:52 ` [PATCH v2 1/2] examples/fips_validation: share test callback with multiple keys Gowrishankar Muthukrishnan
2022-08-12 11:52 ` [PATCH v2 2/2] examples/fips_validation: add parsing for TDES Gowrishankar Muthukrishnan
2022-09-23 16:30 ` Dooley, Brian
2022-10-07 9:55 ` Akhil Goyal [this message]
2022-10-06 13:13 ` [PATCH v2 1/2] examples/fips_validation: share test callback with multiple keys Dooley, Brian
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=CO6PR18MB448411DFFB637D271B6C7F35D85F9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gmuthukrishn@marvell.com \
--cc=jerinj@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).