From: Akhil Goyal <gakhil@marvell.com>
To: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "ciara.power@intel.com" <ciara.power@intel.com>
Subject: RE: [EXTERNAL] [PATCH v5] common/qat: add virtual qat device (vQAT)
Date: Mon, 4 Mar 2024 07:07:20 +0000 [thread overview]
Message-ID: <CO6PR18MB4484E26205370E8AD483A75CD8232@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484020EC7365A57BA4106B4D85E2@CO6PR18MB4484.namprd18.prod.outlook.com>
> Subject: RE: [EXTERNAL] [PATCH v5] common/qat: add virtual qat device (vQAT)
>
> > --- a/doc/guides/rel_notes/release_24_03.rst
> > +++ b/doc/guides/rel_notes/release_24_03.rst
> > @@ -146,6 +146,10 @@ New Features
> > to support TLS v1.2, TLS v1.3 and DTLS v1.2.
> > * Added PMD API to allow raw submission of instructions to CPT.
> >
> > +* **Updated Intel QuickAssist Technology driver.**
> > +
> > + * Enabled support for virtual QAT - vQAT (0da5) devices in QAT PMD.
> > +
> >
> You should add QAT updates under the same bullet which is already there
> for previous updates.
> I will fix it up while applying but you should take care in future.
Applied to dpdk-next-crypto with above update.
Thanks.
next prev parent reply other threads:[~2024-03-04 7:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 13:41 [PATCH 1/2] common/qat: add vqat definition to pmd map Arkadiusz Kusztal
2023-12-18 13:41 ` [PATCH 2/2] common/qat: add vqat confiuration macros Arkadiusz Kusztal
2024-02-18 22:25 ` [PATCH v2] common/qat: add symmetric crypto virtual qat device (vQAT) Arkadiusz Kusztal
2024-02-21 7:50 ` [PATCH v3] common/qat: add " Arkadiusz Kusztal
2024-02-22 12:20 ` Power, Ciara
2024-02-29 10:21 ` [PATCH v4] " Arkadiusz Kusztal
2024-02-29 10:27 ` Power, Ciara
2024-03-01 6:15 ` [EXTERNAL] " Akhil Goyal
2024-03-01 15:19 ` [PATCH v5] " Arkadiusz Kusztal
2024-03-01 15:24 ` [EXTERNAL] " Akhil Goyal
2024-03-04 7:07 ` Akhil Goyal [this message]
2024-03-01 15:48 ` Ji, Kai
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=CO6PR18MB4484E26205370E8AD483A75CD8232@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@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).