Commit 8eea134c authored by Baruch Siach's avatar Baruch Siach Committed by Herbert Xu

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: default avatarBaruch Siach <baruch@tkos.co.il>
Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
parent 450a6c30
...@@ -44,9 +44,6 @@ one block while the former can operate on an arbitrary amount of data, ...@@ -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 subject to block size requirements (i.e., non-stream ciphers can only
process multiples of blocks). 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: Here's an example of how to use the API:
#include <crypto/hash.h> #include <crypto/hash.h>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment