diff options
author | 2025-05-05 13:33:41 -0700 | |
---|---|---|
committer | 2025-05-12 13:33:14 +0800 | |
commit | 40b9969796bfa49ed1b0f7ddc254f48cb2ac6d2c (patch) | |
tree | 3348bf44e9e622851051c1b1d26f7cd8ea12114a /arch/arm | |
parent | crypto: testmgr - remove panic_on_fail (diff) | |
download | wireguard-linux-40b9969796bfa49ed1b0f7ddc254f48cb2ac6d2c.tar.xz wireguard-linux-40b9969796bfa49ed1b0f7ddc254f48cb2ac6d2c.zip |
crypto: testmgr - replace CRYPTO_MANAGER_DISABLE_TESTS with CRYPTO_SELFTESTS
The negative-sense of CRYPTO_MANAGER_DISABLE_TESTS is a longstanding
mistake that regularly causes confusion. Especially bad is that you can
have CRYPTO=n && CRYPTO_MANAGER_DISABLE_TESTS=n, which is ambiguous.
Replace CRYPTO_MANAGER_DISABLE_TESTS with CRYPTO_SELFTESTS which has the
expected behavior.
The tests continue to be disabled by default.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'arch/arm')
-rw-r--r-- | arch/arm/configs/milbeaut_m10v_defconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig index 4ec21f477c63..9dd47e1d90bb 100644 --- a/arch/arm/configs/milbeaut_m10v_defconfig +++ b/arch/arm/configs/milbeaut_m10v_defconfig @@ -94,7 +94,7 @@ CONFIG_NLS_ISO8859_1=y CONFIG_NLS_UTF8=y CONFIG_KEYS=y CONFIG_CRYPTO_MANAGER=y -# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set +CONFIG_CRYPTO_SELFTESTS=y # CONFIG_CRYPTO_ECHAINIV is not set CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_SEQIV=m |