summaryrefslogtreecommitdiff
path: root/backport/compat/Kconfig
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2017-10-13 12:26:23 +0200
committerJohannes Berg <johannes.berg@intel.com>2017-10-13 15:29:52 +0200
commitdeaa397ea3d6c1ae5f7b6c089e8b805c02b293e5 (patch)
treeba6bc6e4439e1e8b40361d1c1e59dcb0e1579d8c /backport/compat/Kconfig
parentb63923298a77174183a7abc9390bae5500703c05 (diff)
backports: remove CRYPTO_CCM backport
This never actually worked properly as far as I can tell, and now it looks like it won't even compile due to the real crypto_memneq() backport. Just remove it - distro kernels have it enabled and all others should just enable it. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'backport/compat/Kconfig')
-rw-r--r--backport/compat/Kconfig11
1 files changed, 0 insertions, 11 deletions
diff --git a/backport/compat/Kconfig b/backport/compat/Kconfig
index 542cf0cc..492efbfc 100644
--- a/backport/compat/Kconfig
+++ b/backport/compat/Kconfig
@@ -102,17 +102,6 @@ config BPAUTO_USERSEL_BUILD_ALL
It's only really useful for compat testing, so
you probably shouldn't enable it.
-config BPAUTO_CRYPTO_CCM
- depends on CRYPTO_AEAD
- depends on CRYPTO_CTR
- bool
-
-config BPAUTO_BUILD_CRYPTO_CCM
- bool
- default n if CRYPTO_CCM
- default y if BPAUTO_CRYPTO_CCM
- #c-file crypto/ccm.c
-
config BPAUTO_CRYPTO_SKCIPHER
tristate
depends on KERNEL_4_3