From: Rosen Penev <rosenp@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: "Boris Brezillon" <bbrezillon@kernel.org>,
"Arnaud Ebalard" <arno@natisbad.org>,
"Srujana Challa" <schalla@marvell.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Rosen Penev" <rosenp@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 1/5] crypto: cesa: add COMPILE_TEST
Date: Tue, 1 Oct 2024 16:25:43 -0700 [thread overview]
Message-ID: <20241001232547.355947-2-rosenp@gmail.com> (raw)
In-Reply-To: <20241001232547.355947-1-rosenp@gmail.com>
This can build on x86. Allows more CI coverage.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
drivers/crypto/marvell/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/marvell/Kconfig b/drivers/crypto/marvell/Kconfig
index 78217577aa54..4c25a78ab3ed 100644
--- a/drivers/crypto/marvell/Kconfig
+++ b/drivers/crypto/marvell/Kconfig
@@ -7,7 +7,7 @@ config CRYPTO_DEV_MARVELL
config CRYPTO_DEV_MARVELL_CESA
tristate "Marvell's Cryptographic Engine driver"
- depends on PLAT_ORION || ARCH_MVEBU
+ depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST
select CRYPTO_LIB_AES
select CRYPTO_LIB_DES
select CRYPTO_SKCIPHER
--
2.46.2
next prev parent reply other threads:[~2024-10-01 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 23:25 [PATCH 0/5] cesa: small cleanups Rosen Penev
2024-10-01 23:25 ` Rosen Penev [this message]
2024-10-01 23:25 ` [PATCH 2/5] crypto: cesa: use enabled variants for clk_get Rosen Penev
2024-10-03 11:27 ` Dan Carpenter
2024-10-01 23:25 ` [PATCH 3/5] crypto: cesa: remove irq_set_affinity_hint Rosen Penev
2024-10-01 23:25 ` [PATCH 4/5] crypto: cesa: move loop to mv_cesa_put_sram Rosen Penev
2024-10-01 23:25 ` [PATCH 5/5] crypto: use devm_platform_get_and_ioremap_resource Rosen Penev
-- strict thread matches above, loose matches on Subject: below --
2024-10-03 9:20 [PATCH 1/5] crypto: cesa: add COMPILE_TEST kernel test robot
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=20241001232547.355947-2-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schalla@marvell.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.