DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Ji, Kai" <kai.ji@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: RE: [PATCH v2 1/3] crypto/qat: fix uncleared cookies in asym
Date: Fri, 21 Oct 2022 13:29:33 +0000	[thread overview]
Message-ID: <PH0PR18MB44913A8D949ABB0634440FD1D82D9@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB3821DC38BA32F51F62CD12FEE62D9@MN2PR11MB3821.namprd11.prod.outlook.com>

> > Subject: [PATCH v2 1/3] crypto/qat: fix uncleared cookies in asym
> >
> > Fixed incorrectly placed clean function in asym response.
> >
> > Fixes: 002486db239e ("crypto/qat: refactor asymmetric session")
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > ---
> > v2:
> > - fixed compilation issues
> > - split into 3 patches
> >
> <snip>
> 
> Acked-by: Ciara Power <ciara.power@intel.com>

Series applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2022-10-21 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 13:53 Arek Kusztal
2022-10-18 13:53 ` [PATCH v2 2/3] crypto/qat: fix unnecessary session check Arek Kusztal
2022-10-21  8:29   ` Power, Ciara
2022-10-18 13:53 ` [PATCH v2 3/3] crypto/qat: fix not set rsa lengths Arek Kusztal
2022-10-21  8:29   ` Power, Ciara
2022-10-21  8:29 ` [PATCH v2 1/3] crypto/qat: fix uncleared cookies in asym Power, Ciara
2022-10-21 13:29   ` 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=PH0PR18MB44913A8D949ABB0634440FD1D82D9@PH0PR18MB4491.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ciara.power@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).