summaryrefslogtreecommitdiffstats
path: root/drivers/net
diff options
context:
space:
mode:
authorMatthieu Baerts <matthieu.baerts@tessares.net>2020-02-15 15:45:56 +0100
committerDavid S. Miller <davem@davemloft.net>2020-02-16 19:37:16 -0800
commit357b41caf949c57e426f1c5f18574b6b46583406 (patch)
treebb94d9272ec11db6be4d6705dfe40a988861127f /drivers/net
parentc230978fb7d59d69ce6992623d948fb84abbf9e6 (diff)
downloadlinux-357b41caf949c57e426f1c5f18574b6b46583406.tar.gz
linux-357b41caf949c57e426f1c5f18574b6b46583406.tar.bz2
linux-357b41caf949c57e426f1c5f18574b6b46583406.zip
mptcp: select CRYPTO
Without this modification and if CRYPTO is not selected, we have this warning: WARNING: unmet direct dependencies detected for CRYPTO_LIB_SHA256 Depends on [n]: CRYPTO [=n] Selected by [y]: - MPTCP [=y] && NET [=y] && INET [=y] MPTCP selects CRYPTO_LIB_SHA256 which seems to depend on CRYPTO. CRYPTO is now selected to avoid this issue. Even though the config system prints that warning, it looks like sha256.c is compiled and linked even without CONFIG_CRYPTO. Since MPTCP will end up needing CONFIG_CRYPTO anyway in future commits -- currently in preparation for net-next -- we propose to add it now to fix the warning. The dependency in the config system comes from the fact that CRYPTO_LIB_SHA256 is defined in "lib/crypto/Kconfig" which is sourced from "crypto/Kconfig" only if CRYPTO is selected. Fixes: 65492c5a6ab5 (mptcp: move from sha1 (v0) to sha256 (v1)) Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions