summaryrefslogtreecommitdiff
path: root/crypto/lz4.c
diff options
context:
space:
mode:
authorJean Delvare <jdelvare@suse.de>2016-01-18 17:06:05 +0100
committerHerbert Xu <herbert@gondor.apana.org.au>2016-01-19 15:52:10 +0800
commit0a9e44e9ab8d7640b9792ac6bebe640cc607318b (patch)
treef551a4d87c51cd995735f5506a36b30578beeada /crypto/lz4.c
parent266a9ee25fc2d3b966f047c3d8588d89ac41043c (diff)
downloadlinux-crypto-0a9e44e9ab8d7640b9792ac6bebe640cc607318b.tar.gz
linux-crypto-0a9e44e9ab8d7640b9792ac6bebe640cc607318b.zip
crypto: crc32c - Fix crc32c soft dependency
I don't think it makes sense for a module to have a soft dependency on itself. This seems quite cyclic by nature and I can't see what purpose it could serve. OTOH libcrc32c calls crypto_alloc_shash("crc32c", 0, 0) so it pretty much assumes that some incarnation of the "crc32c" hash algorithm has been loaded. Therefore it makes sense to have the soft dependency there (as crc-t10dif does.) Cc: stable@vger.kernel.org Cc: Tim Chen <tim.c.chen@linux.intel.com> Cc: "David S. Miller" <davem@davemloft.net> Signed-off-by: Jean Delvare <jdelvare@suse.de> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/lz4.c')
0 files changed, 0 insertions, 0 deletions