From: sashiko-bot@kernel.org
To: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Russell King" <linux@armlinux.org.uk>,
"Eric Biggers" <ebiggers@kernel.org>,
"Demi Marie Obenour" <demiobenour@gmail.com>,
"Kuldeep Singh" <kuldeep.singh@oss.qualcomm.com>,
"Pankaj Patil" <pankaj.patil@oss.qualcomm.com>,
"Birk Skyum" <birk.skyum@pm.me>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH v11 1/2] crypto: qce - Only register algos if the user really wants it
Date: Thu, 22 Oct 2026 09:05:01 +0000 [thread overview]
Message-ID: <sashiko-outbox-181233@kernel.org> (raw)
In-Reply-To: <20261022-qce-fixes-broken-label-v11-1-0d33c34fd0c3@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] crypto: qce: missing kernel-parameters.txt doc for do_register_algos
--
commit 47675c12b3c6637f5e62afe90e1fb4f153328b57
Author: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
crypto: qce - Only register algos if the user really wants it
This commit adds a do_register_algos module parameter to the QCE crypto
driver so that crypto algorithms are not registered by default during
probe unless explicitly enabled by the user.
> diff --git a/drivers/crypto/qce/core.c b/drivers/crypto/qce/core.c
> index bf3c1bc3ba7bd..5b1bf7a50f88c 100644
> --- a/drivers/crypto/qce/core.c
> +++ b/drivers/crypto/qce/core.c
[ ... ]
> @@ -22,6 +23,9 @@
> #include "sha.h"
> #include "aead.h"
>
> +static bool do_register_algos;
> +module_param(do_register_algos, bool, 0444);
[Severity: Low]
In drivers/crypto/qce/core.c, module_param(do_register_algos, bool, 0444)
exposes qcrypto.do_register_algos as a kernel command-line and module
parameter to gate devm_qce_register_algs(qce) in qce_crypto_probe().
Should Documentation/admin-guide/kernel-parameters.txt also be updated to
document qcrypto.do_register_algos, along with a parameter description in
drivers/crypto/qce/core.c?
> +
> #define QCE_QUEUE_LENGTH 1
>
> #define QCE_DEFAULT_MEM_BANDWIDTH 393600
> @@ -259,9 +263,11 @@ static int qce_crypto_probe(struct platform_device *pdev)
> qce->async_req_enqueue = qce_async_request_enqueue;
> qce->async_req_done = qce_async_request_done;
>
> - ret = devm_qce_register_algs(qce);
> - if (ret)
> - return ret;
> + if (do_register_algos) {
> + ret = devm_qce_register_algs(qce);
> + if (ret)
> + return ret;
> + }
>
> /* Configure autosuspend after successful init */
> pm_runtime_set_autosuspend_delay(dev, 100);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261022-qce-fixes-broken-label-v11-0-0d33c34fd0c3@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-10-22 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 8:57 [PATCH v11 0/2] crypto - qce: make algos optional and remove the BROKEN label Bartosz Golaszewski
2026-10-22 8:57 ` [PATCH v11 1/2] crypto: qce - Only register algos if the user really wants it Bartosz Golaszewski
2026-10-22 9:04 ` Konrad Dybcio
2026-10-22 9:05 ` sashiko-bot [this message]
2026-10-22 8:58 ` [PATCH v11 2/2] Revert "crypto: qce - Mark QCE as BROKEN" Bartosz Golaszewski
2026-10-22 9:04 ` Konrad Dybcio
2026-10-22 9:07 ` sashiko-bot
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=sashiko-outbox-181233@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=birk.skyum@pm.me \
--cc=brgl@kernel.org \
--cc=davem@davemloft.net \
--cc=demiobenour@gmail.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.