tpm: select CONFIG_CRYPTO
authorArnd Bergmann <arnd@arndb.de>
Tue, 28 Feb 2017 21:12:55 +0000 (22:12 +0100)
committerJarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Mon, 3 Apr 2017 19:46:00 +0000 (22:46 +0300)
We get a newly introduced harmless warning when CONFIG_CRYPTO is disabled:

warning: (TCG_TPM && TRUSTED_KEYS && IMA) selects CRYPTO_HASH_INFO which has unmet direct dependencies (CRYPTO)

This adds another select to avoid the warning, consistent with other users
of the crypto code.

Fixes: c1f92b4b04ad ("tpm: enhance TPM 2.0 PCR extend to support multiple banks")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Peter Huewe <peterhuewe@gmx.de>
Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
drivers/char/tpm/Kconfig

index af985cca413cbfef089f88aea1767c3e26bb18e1..d520ac51c11c2a778a069080a00376af517476af 100644 (file)
@@ -6,6 +6,7 @@ menuconfig TCG_TPM
        tristate "TPM Hardware Support"
        depends on HAS_IOMEM
        select SECURITYFS
+       select CRYPTO
        select CRYPTO_HASH_INFO
        ---help---
          If you have a TPM security chip in your system, which