From b51e236f1a1e25620d445a2b43c598a5917ba379 Mon Sep 17 00:00:00 2001 From: Aelin Date: Wed, 22 Apr 2026 22:49:56 +0200 Subject: [PATCH] kconfigcheck: Fix inconsistencies on loongarch64 CONFIG_CRYPTO_CTS is built-in if CONFIG_FS_ENCRYPTION is enabled, which it is by default on loongarch64, which is reasonable. CONFIG_NFSD is also built-in on some architectures, which causes CONFIG_RPCSEC_GSS_KRB5 to be built-in rather than a module. We could either force disable NFSD, which is not great, or just build it as a module, which is what I opted for. Part-of: --- kconfigcheck.toml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/kconfigcheck.toml b/kconfigcheck.toml index 5730eabf5..c872e5e3f 100644 --- a/kconfigcheck.toml +++ b/kconfigcheck.toml @@ -123,7 +123,7 @@ UTS_NS = "y" ["category:netmount".">=2.6.0"."all"] CACHEFILES = "m" CRYPTO_CAMELLIA = "m" -CRYPTO_CTS = "m" +CRYPTO_CTS = "y" CRYPTO_HMAC = "y" CRYPTO_SHA256 = "y" CRYPTO_SHA512 = "y" @@ -132,6 +132,7 @@ NFS_FS = "m" NFS_FSCACHE = "y" NFS_V3 = "m" NFS_V4 = "m" +NFSD = "m" RPCSEC_GSS_KRB5 = "m" ["category:netmount".">=3.1.0"."all"] CRYPTO_CMAC = "m"