All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dooley, Brian" <brian.dooley@intel.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
	"Ji, Kai" <kai.ji@intel.com>
Subject: RE: [EXT] [PATCH v4] examples/fips_validation: add parsing for AES CTR
Date: Mon, 10 Oct 2022 14:29:39 +0000	[thread overview]
Message-ID: <CY4PR11MB1848FF4D30E6A9F308FEE6A783209@CY4PR11MB1848.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB448491ABBFE1F25A9E3C5127D85F9@CO6PR18MB4484.namprd18.prod.outlook.com>

Hi Akhil,

> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Friday, October 7, 2022 11:49 AM
> To: Dooley, Brian <brian.dooley@intel.com>
> Cc: dev@dpdk.org; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>; roy.fan.zhang@intel.com; Ji, Kai
> <kai.ji@intel.com>
> Subject: RE: [EXT] [PATCH v4] examples/fips_validation: add parsing for AES
> CTR
> 
> Hi Brian,
> > 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
> > ---
> >  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 +++++++--
> >  4 files changed, 16 insertions(+), 2 deletions(-)
> Can you also update doc/guides/sample_app_ug/fips_validation.rst for CTR
> and GMAC that you have added.

Docs now updated in latest version


  reply	other threads:[~2022-10-10 14:29 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
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 [this message]
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=CY4PR11MB1848FF4D30E6A9F308FEE6A783209@CY4PR11MB1848.namprd11.prod.outlook.com \
    --to=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=gmuthukrishn@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.