All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>,
	"Dooley, Brian" <brian.dooley@intel.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: RE: [PATCH v2] examples/fips_validation: add parsing for AES CTR
Date: Fri, 16 Sep 2022 17:23:47 +0000	[thread overview]
Message-ID: <CO1PR18MB47140A5A5A8A50A34306FA29CB489@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB34081D2ADD71545DE4E565F681499@SN6PR11MB3408.namprd11.prod.outlook.com>

Tested with FIPS test vectors from NIST.

Acked-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>

Thanks,
Gowrishankar

> -----Original Message-----
> From: Ji, Kai <kai.ji@intel.com>
> Sent: Thursday, September 15, 2022 6:52 PM
> To: Dooley, Brian <brian.dooley@intel.com>; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>
> Cc: dev@dpdk.org; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>; Akhil Goyal <gakhil@marvell.com>
> Subject: [EXT] RE: [PATCH v2] examples/fips_validation: add parsing for AES
> CTR
> 
> External Email
> 
> ----------------------------------------------------------------------
> Please fix the checkpath issue reported.
> 
> Acked-by: Ji, Kai <kai.ji@intel.com>
> 
> > -----Original Message-----
> > From: Dooley, Brian <brian.dooley@intel.com>
> > Sent: Monday, August 22, 2022 1:23 PM
> > To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; Dooley, Brian
> > <brian.dooley@intel.com>
> > Cc: dev@dpdk.org; gmuthukrishn@marvell.com; gakhil@marvell.com; Ji,
> > Kai <kai.ji@intel.com>
> > Subject: [PATCH v2] examples/fips_validation: add parsing for AES CTR
> >
> > Added functionality to parse algorithm for AES CTR test
> >
> > Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> > ---
> > v2: fix clang warning for int-in-bool-context
> > ---

  reply	other threads:[~2022-09-16 17:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 12:23 [PATCH v2] examples/fips_validation: add parsing for AES CTR Brian Dooley
2022-09-15 13:21 ` Ji, Kai
2022-09-16 17:23   ` Gowrishankar Muthukrishnan [this message]
2022-09-16 13:53 ` [PATCH v3] " Brian Dooley
2022-09-30  8:53   ` [PATCH v4] " Brian Dooley
2022-10-07 10:48     ` [EXT] " Akhil Goyal
2022-10-10 14:29       ` Dooley, Brian
2022-10-10 15:51         ` Akhil Goyal
2022-10-07 16:58     ` [PATCH v5] " Brian Dooley
2022-10-10 19:49       ` [EXT] " 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=CO1PR18MB47140A5A5A8A50A34306FA29CB489@CO1PR18MB4714.namprd18.prod.outlook.com \
    --to=gmuthukrishn@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.