From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>,
"Ji, Kai" <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ji, Kai" <kai.ji@intel.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [dpdk-dev v1] crypto/qat: fix of qat build request session in mp
Date: Thu, 27 Oct 2022 09:53:42 +0000 [thread overview]
Message-ID: <CO6PR18MB4484C05B3974766DF3BC178CD8339@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB3821B0BE74EF82269F424B51E65F9@MN2PR11MB3821.namprd11.prod.outlook.com>
> > Subject: [dpdk-dev v1] crypto/qat: fix of qat build request session in mp
> >
> > This patch fix the session pointer passed in set_session() when ctx has NULL
> > build request pointer in multi-processes scenario.
> >
> > Fixes: fb3b9f492205 ("crypto/qat: rework burst data path")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Kai Ji <kai.ji@intel.com>
> > ---
>
> Acked-by: Ciara Power <ciara.power@intel.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-10-27 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 16:08 Kai Ji
2022-10-07 14:21 ` Power, Ciara
2022-10-27 9: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=CO6PR18MB4484C05B3974766DF3BC178CD8339@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=stable@dpdk.org \
/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).