docs: crypto_engine.rst: Fix two parse warnings
./Documentation/crypto/crypto_engine.rst:13: WARNING: Unexpected indentation. ./Documentation/crypto/crypto_engine.rst:15: WARNING: Block quote ends without a blank line; unexpected unindent. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> Acked-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
b701745097
commit
2fab30199a
1 changed files with 5 additions and 3 deletions
|
@ -8,11 +8,13 @@ The crypto engine API (CE), is a crypto queue manager.
|
||||||
|
|
||||||
Requirement
|
Requirement
|
||||||
-----------
|
-----------
|
||||||
You have to put at start of your tfm_ctx the struct crypto_engine_ctx
|
You have to put at start of your tfm_ctx the struct crypto_engine_ctx::
|
||||||
struct your_tfm_ctx {
|
|
||||||
|
struct your_tfm_ctx {
|
||||||
struct crypto_engine_ctx enginectx;
|
struct crypto_engine_ctx enginectx;
|
||||||
...
|
...
|
||||||
};
|
};
|
||||||
|
|
||||||
Why: Since CE manage only crypto_async_request, it cannot know the underlying
|
Why: Since CE manage only crypto_async_request, it cannot know the underlying
|
||||||
request_type and so have access only on the TFM.
|
request_type and so have access only on the TFM.
|
||||||
So using container_of for accessing __ctx is impossible.
|
So using container_of for accessing __ctx is impossible.
|
||||||
|
|
Loading…
Reference in a new issue