aboutsummaryrefslogtreecommitdiff
path: root/Documentation/crypto
diff options
context:
space:
mode:
authorBaruch Siach2016-11-30 15:16:10 +0200
committerHerbert Xu2016-12-01 21:06:34 +0800
commit8eea134c3787c731223f0f88ae35874ab06232d4 (patch)
tree186e6832d57f880f331eea83b8cca38d1d54a0bf /Documentation/crypto
parent450a6c30ef3bbedcb4af3d9eab0df24929d5db4a (diff)
crypt: doc - remove misleading mention of async API
The asynchronous API is quite mature. Not mentioning is at all is probably better than saying it is under development. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'Documentation/crypto')
-rw-r--r--Documentation/crypto/api-intro.txt3
1 files changed, 0 insertions, 3 deletions
diff --git a/Documentation/crypto/api-intro.txt b/Documentation/crypto/api-intro.txt
index 96bd46033d28..45d943fcae5b 100644
--- a/Documentation/crypto/api-intro.txt
+++ b/Documentation/crypto/api-intro.txt
@@ -44,9 +44,6 @@ one block while the former can operate on an arbitrary amount of data,
subject to block size requirements (i.e., non-stream ciphers can only
process multiples of blocks).
-Support for hardware crypto devices via an asynchronous interface is
-under development.
-
Here's an example of how to use the API:
#include <crypto/hash.h>