summaryrefslogtreecommitdiff
path: root/include/crypto
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2019-08-17 17:24:33 +0300
committerHerbert Xu <herbert@gondor.apana.org.au>2019-08-22 07:57:35 +0300
commit01d3aee86625bd798a5e69afb92517d5530c7ed1 (patch)
treeaf7a77af65f727f130f7dc8bf40649cf1701f666 /include/crypto
parent906a4bb97f5d0389cae9cc3634e8059fed5334b5 (diff)
downloadlinux-01d3aee86625bd798a5e69afb92517d5530c7ed1.tar.xz
crypto: sha256 - Make lib/crypto/sha256.c suitable for generic use
Before this commit lib/crypto/sha256.c has only been used in the s390 and x86 purgatory code, make it suitable for generic use: * Export interesting symbols * Add -D__DISABLE_EXPORTS to CFLAGS_sha256.o for purgatory builds to avoid the exports for the purgatory builds * Add to lib/crypto/Makefile and crypto/Kconfig Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'include/crypto')
-rw-r--r--include/crypto/sha256.h5
1 files changed, 3 insertions, 2 deletions
diff --git a/include/crypto/sha256.h b/include/crypto/sha256.h
index b1f9c6781082..9cbb3589b8b3 100644
--- a/include/crypto/sha256.h
+++ b/include/crypto/sha256.h
@@ -14,8 +14,9 @@
/*
* Stand-alone implementation of the SHA256 algorithm. It is designed to
* have as little dependencies as possible so it can be used in the
- * kexec_file purgatory. In other cases you should use the implementation in
- * crypto/.
+ * kexec_file purgatory. In other cases you should generally use the
+ * hash APIs from include/crypto/hash.h. Especially when hashing large
+ * amounts of data as those APIs may be hw-accelerated.
*
* For details see lib/crypto/sha256.c
*/