DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2 0/2] crypto/qat: add secp384r1 curve support
Date: Thu, 26 May 2022 16:53:42 +0000	[thread overview]
Message-ID: <CO6PR18MB4484C923C1D3809952BC316BD8D99@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB58098EDBF8ADE9485B3046BBB8C99@MW5PR11MB5809.namprd11.prod.outlook.com>

> > This patchset adds secp384r1 (P-384) elliptic
> > curve to Intel QuickAssist Technology crypto PMD.
> >
> > v2:
> > - added release notes
> >
> > Arek Kusztal (2):
> >   crypto/qat: refactor asym algorithm macros and logs
> >   crypto/qat: add secp384r1 curve
> >
> >  doc/guides/rel_notes/release_22_07.rst |   4 +
> >  drivers/common/qat/qat_adf/qat_pke.h   |  12 ++
> >  drivers/crypto/qat/qat_asym.c          | 230 ++++++++++++++-------------------
> >  drivers/crypto/qat/qat_asym.h          |   3 +-
> >  drivers/crypto/qat/qat_ec.h            |  77 ++++++++++-
> >  5 files changed, 193 insertions(+), 133 deletions(-)
> >
> > --
> > 2.13.6
> Series-acked-by: Fan Zhang <roy.fan.zhang@intel.com>

Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2022-05-26 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22  9:33 Arek Kusztal
2022-04-22  9:33 ` [PATCH v2 1/2] crypto/qat: refactor asym algorithm macros and logs Arek Kusztal
2022-05-10 10:08   ` Zhang, Roy Fan
2022-04-22  9:33 ` [PATCH v2 2/2] crypto/qat: add secp384r1 curve Arek Kusztal
2022-05-10 10:10   ` Zhang, Roy Fan
2022-05-10 10:10 ` [PATCH v2 0/2] crypto/qat: add secp384r1 curve support Zhang, Roy Fan
2022-05-26 16:53   ` Akhil Goyal [this message]

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=CO6PR18MB4484C923C1D3809952BC316BD8D99@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --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).