DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] crypto/qat: enable asymmetric crypto on gen4 device
Date: Thu, 26 May 2022 16:33:24 +0000	[thread overview]
Message-ID: <CO6PR18MB448464906960AB3FEDE6493BD8D99@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB34085F4AFACDBD703FC48A1B81C99@SN6PR11MB3408.namprd11.prod.outlook.com>

> Acked-by: Ji, Kai <kai.ji@intel.com>
Please be consistent in Acks
Corrected this to 
Acked-by: Kai Ji <kai.ji@intel.com>

> 
> > This commit enables asymmetric crypto in generation four devices (4xxx).
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>

Applied to dpdk-next-crypto

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  9:47 Arek Kusztal
2022-05-10 14:59 ` Ji, Kai
2022-05-26 16:33   ` 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=CO6PR18MB448464906960AB3FEDE6493BD8D99@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@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).