summaryrefslogtreecommitdiffstats
path: root/drivers/rapidio/rio-scan.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2017-02-06 13:32:15 +0100
committerHerbert Xu <herbert@gondor.apana.org.au>2017-02-11 10:52:29 +0100
commitceb4afb3086ab08f0d1d9cb3da536a18ea2e5918 (patch)
tree2b716a72324de8ad7de1bac09ab72ba2140b0a55 /drivers/rapidio/rio-scan.c
parentcrypto: algapi - make crypto_xor() and crypto_inc() alignment agnostic (diff)
downloadlinux-ceb4afb3086ab08f0d1d9cb3da536a18ea2e5918.tar.xz
linux-ceb4afb3086ab08f0d1d9cb3da536a18ea2e5918.zip
crypto: atmel - refine Kconfig dependencies
With the new authenc support, we get a harmless Kconfig warning: warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has unmet direct dependencies (CRYPTO && CRYPTO_HW && ARCH_AT91) The problem is that each of the options has slightly different dependencies, although they all seem to want the same thing: allow building for real AT91 targets that actually have the hardware, and possibly for compile testing. This makes all four options consistent: instead of depending on a particular dmaengine implementation, we depend on the ARM platform, CONFIG_COMPILE_TEST as an alternative when that is turned off. This makes the 'select' statements work correctly. Fixes: 89a82ef87e01 ("crypto: atmel-authenc - add support to authenc(hmac(shaX), Y(aes)) modes") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/rapidio/rio-scan.c')
0 files changed, 0 insertions, 0 deletions