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 v3 1/2] common/qat: read hw slice configuration
Date: Fri, 21 Oct 2022 13:39:21 +0000 [thread overview]
Message-ID: <PH0PR18MB4491C36762A435618CA41D27D82D9@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB34084C24AC296A7F8F6DAF97812A9@SN6PR11MB3408.namprd11.prod.outlook.com>
> Acked-by: Kai Ji <kai.ji@intel.com>
> > Subject: [PATCH v3 1/2] common/qat: read hw slice configuration
> >
> > Read slice configuration of QAT capabilities.
> > This will allow to recognize if specific hw function is available on particular
> > device.
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Series applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-10-21 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:01 Arek Kusztal
2022-10-18 14:01 ` [PATCH v3 2/2] crypto/qat: " Arek Kusztal
2022-10-20 14:09 ` Ji, Kai
2022-10-20 14:08 ` [PATCH v3 1/2] common/qat: " Ji, Kai
2022-10-21 13:39 ` 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=PH0PR18MB4491C36762A435618CA41D27D82D9@PH0PR18MB4491.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).