From: Vinod Koul <vkoul@kernel.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
fenghua.yu@intel.com, dave.jiang@intel.com, tony.luck@intel.com,
wajdi.k.feghali@intel.com, james.guilford@intel.com,
kanchana.p.sridhar@intel.com, vinodh.gopal@intel.com,
giovanni.cabiddu@intel.com, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH v8 05/14] dmaengine: idxd: Export wq resource management functions
Date: Thu, 3 Aug 2023 18:47:25 +0530 [thread overview]
Message-ID: <ZMuo5eNJgKmBog6p@matsya> (raw)
In-Reply-To: <20230731212939.1391453-6-tom.zanussi@linux.intel.com>
On 31-07-23, 16:29, Tom Zanussi wrote:
> To allow idxd sub-drivers to access the wq resource management
> functions, export them.
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2023-08-03 13:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 21:29 [PATCH v8 00/14] crypto: Add Intel Analytics Accelerator (IAA) crypto compression driver Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 01/14] dmaengine: idxd: add wq driver name support for accel-config user tool Tom Zanussi
2023-08-02 15:17 ` Fenghua Yu
2023-08-02 16:58 ` Tom Zanussi
2023-08-03 11:36 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 02/14] dmaengine: idxd: add external module driver support for dsa_bus_type Tom Zanussi
2023-08-03 13:14 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 03/14] dmaengine: idxd: Export drv_enable/disable and related functions Tom Zanussi
2023-08-03 13:15 ` Vinod Koul
2023-08-03 14:24 ` Tom Zanussi
2023-08-03 15:24 ` Dave Jiang
2023-07-31 21:29 ` [PATCH v8 04/14] dmaengine: idxd: Export descriptor management functions Tom Zanussi
2023-08-03 13:16 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 05/14] dmaengine: idxd: Export wq resource " Tom Zanussi
2023-08-03 13:17 ` Vinod Koul [this message]
2023-07-31 21:29 ` [PATCH v8 06/14] dmaengine: idxd: Add wq private data accessors Tom Zanussi
2023-08-03 13:17 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 07/14] dmaengine: idxd: add callback support for iaa crypto Tom Zanussi
2023-08-03 13:19 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 08/14] crypto: iaa - Add IAA Compression Accelerator Documentation Tom Zanussi
2023-08-21 17:21 ` Pavel Machek
2023-08-21 18:44 ` Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 09/14] crypto: iaa - Add Intel IAA Compression Accelerator crypto driver core Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 10/14] crypto: iaa - Add per-cpu workqueue table with rebalancing Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 11/14] crypto: iaa - Add compression mode management along with fixed mode Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 12/14] crypto: iaa - Add support for deflate-iaa compression algorithm Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 13/14] crypto: iaa - Add irq support for the crypto async interface Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 14/14] crypto: iaa - Add IAA Compression Accelerator stats Tom Zanussi
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=ZMuo5eNJgKmBog6p@matsya \
--to=vkoul@kernel.org \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=james.guilford@intel.com \
--cc=kanchana.p.sridhar@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.zanussi@linux.intel.com \
--cc=tony.luck@intel.com \
--cc=vinodh.gopal@intel.com \
--cc=wajdi.k.feghali@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).