DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Ji, Kai" <kai.ji@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>,
	"Dooley, Brian" <brian.dooley@intel.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Subject: RE: [v1 1/2] cryptodev: add enumeration in EC xform for FPM
Date: Fri, 30 Sep 2022 18:08:42 +0000	[thread overview]
Message-ID: <CO6PR18MB448448D21A2EA3C3949C9BA3D8569@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB3408787CE99C2E9B8ACE344B81549@SN6PR11MB3408.namprd11.prod.outlook.com>


> Acked-by: Kai Ji <kai.ji@intel.com>
> 
> > Add enumeration in EC xform for FPM. Crypto driver would need this to
> > xform point multiplication based on given type of EC curve.
> >
> > Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> > Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> > ---

This patch is applied to dpdk-next-crypto as we are approaching RC1 date.

FIPS application patch is not acked and we can merge it in RC2.


  reply	other threads:[~2022-09-30 18:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  7:30 [v1 0/2] examples/fips_validation: add ECDSA tests Gowrishankar Muthukrishnan
2022-09-27  7:30 ` [v1 1/2] cryptodev: add enumeration in EC xform for FPM Gowrishankar Muthukrishnan
2022-09-28 21:35   ` Ji, Kai
2022-09-30 18:08     ` Akhil Goyal [this message]
2022-09-27  7:30 ` [v1 2/2] examples/fips_validation: add ECDSA validation Gowrishankar Muthukrishnan
2022-10-07 10:50   ` Akhil Goyal
2022-10-17  9:34   ` Dooley, Brian
2022-10-21 15:48     ` 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=CO6PR18MB448448D21A2EA3C3949C9BA3D8569@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=kai.ji@intel.com \
    --cc=kirankumark@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).