From: Barry Song <21cnbao@gmail.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Barry Song <v-songbaohua@oppo.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH v2 2/2] crypto: iaa - fix the missing CRYPTO_ALG_ASYNC in cra_flags
Date: Thu, 29 Feb 2024 23:14:49 +1300 [thread overview]
Message-ID: <20240229101449.227921-3-21cnbao@gmail.com> (raw)
In-Reply-To: <20240229101449.227921-1-21cnbao@gmail.com>
From: Barry Song <v-songbaohua@oppo.com>
Add the missing CRYPTO_ALG_ASYNC flag since intel iaa driver
works asynchronously.
Signed-off-by: Barry Song <v-songbaohua@oppo.com>
Acked-by: Tom Zanussi <tom.zanussi@linux.intel.com>
---
drivers/crypto/intel/iaa/iaa_crypto_main.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/crypto/intel/iaa/iaa_crypto_main.c b/drivers/crypto/intel/iaa/iaa_crypto_main.c
index dfd3baf0a8d8..91adf9d76a2e 100644
--- a/drivers/crypto/intel/iaa/iaa_crypto_main.c
+++ b/drivers/crypto/intel/iaa/iaa_crypto_main.c
@@ -1916,6 +1916,7 @@ static struct acomp_alg iaa_acomp_fixed_deflate = {
.base = {
.cra_name = "deflate",
.cra_driver_name = "deflate-iaa",
+ .cra_flags = CRYPTO_ALG_ASYNC,
.cra_ctxsize = sizeof(struct iaa_compression_ctx),
.cra_module = THIS_MODULE,
.cra_priority = IAA_ALG_PRIORITY,
--
2.34.1
next prev parent reply other threads:[~2024-02-29 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 10:14 [PATCH v2 0/2] [PATCH v2 0/2] crypto: fix missing CRYPTO_ALG_ASYNC for async drivers Barry Song
2024-02-29 10:14 ` [PATCH v2 1/2] crypto: hisilicon/zip - fix the missing CRYPTO_ALG_ASYNC in cra_flags Barry Song
2024-02-29 10:14 ` Barry Song [this message]
2024-03-01 19:33 ` [PATCH v2 0/2] [PATCH v2 0/2] crypto: fix missing CRYPTO_ALG_ASYNC for async drivers Barry Song
2024-03-08 11:25 ` Herbert Xu
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=20240229101449.227921-3-21cnbao@gmail.com \
--to=21cnbao@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.zanussi@linux.intel.com \
--cc=v-songbaohua@oppo.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).