From: "Dooley, Brian" <brian.dooley@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
"Power, Ciara" <ciara.power@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: RE: [PATCH v5 2/3] common/qat: decouple pmds from the common code
Date: Fri, 1 Mar 2024 16:08:00 +0000 [thread overview]
Message-ID: <SJ0PR11MB5056B269748F48E4C72A80DC835E2@SJ0PR11MB5056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240301155251.5101-2-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> Sent: Friday, March 1, 2024 3:53 PM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Power, Ciara <ciara.power@intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v5 2/3] common/qat: decouple pmds from the common
> code
>
> Service specific functions were moved to services files. Weak symbols for
> device create/destroy were removed, named private devs were replaced by an
> opaque array.
>
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> drivers/common/qat/qat_device.c | 112 ++++++++++-------------------------
> -
> drivers/common/qat/qat_device.h | 47 ++++-----------
> drivers/compress/qat/qat_comp_pmd.c | 34 +++++------
> drivers/compress/qat/qat_comp_pmd.h | 7 ---
> drivers/crypto/qat/qat_asym.c | 20 ++++---
> drivers/crypto/qat/qat_sym.c | 19 +++---
> 6 files changed, 83 insertions(+), 156 deletions(-)
>
<snip>
Acked-by: Brian Dooley <brian.dooley@intel.com>
next prev parent reply other threads:[~2024-03-01 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v4-00020240229093007.32298-1-arkadiuszx.kusztal@intel.com>
2024-02-29 19:14 ` [PATCH v4 1/3] common/qat: isolate parser arguments configuration Arkadiusz Kusztal
2024-02-29 19:14 ` [PATCH v4 2/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-02-29 19:14 ` [PATCH v4 3/3] common/qat: fix incorrectly placed legacy flag Arkadiusz Kusztal
2024-02-29 19:19 ` [EXTERNAL] [PATCH v4 1/3] common/qat: isolate parser arguments configuration Akhil Goyal
2024-03-01 15:52 ` [PATCH v5 " Arkadiusz Kusztal
2024-03-01 15:52 ` [PATCH v5 2/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-03-01 16:08 ` Dooley, Brian [this message]
2024-03-01 15:52 ` [PATCH v5 3/3] common/qat: fix incorrectly placed legacy flag Arkadiusz Kusztal
2024-03-01 16:08 ` Dooley, Brian
2024-03-04 7:10 ` Akhil Goyal
2024-03-01 16:07 ` [PATCH v5 1/3] common/qat: isolate parser arguments configuration Dooley, Brian
2024-03-04 7:08 ` [EXTERNAL] " Akhil Goyal
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=SJ0PR11MB5056B269748F48E4C72A80DC835E2@SJ0PR11MB5056.namprd11.prod.outlook.com \
--to=brian.dooley@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.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).