From: Joe Perches <joe@perches.com>
To: "Hook, Gary" <Gary.Hook@amd.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH v2 2/2] crypto: doc - Fix formatting of new crypto engine content
Date: Tue, 25 Jun 2019 17:13:25 -0700 [thread overview]
Message-ID: <983486e9b2daaa34f84f99a890fcedfeae22b24f.camel@perches.com> (raw)
In-Reply-To: <156150622886.22527.934327975584441429.stgit@taos>
On Tue, 2019-06-25 at 23:43 +0000, Hook, Gary wrote:
> Tidy up the formatting/grammar in crypto_engine.rst. Use bulleted lists
> where appropriate.
Hi again Gary.
> diff --git a/Documentation/crypto/crypto_engine.rst b/Documentation/crypto/crypto_engine.rst
[]
> +Before transferring any request, you have to fill the context enginectx by
> +providing functions for the following:
> +
> +* ``prepare_crypt_hardware``: Called once before any prepare functions are
> + called.
> +
> +* ``unprepare_crypt_hardware``: Called once after all unprepare functions have
> + been called.
> +
> +* ``prepare_cipher_request``/``prepare_hash_request``: Called before each
> + corresponding request is performed. If some processing or other preparatory
> + work is required, do it here.
> +
> +* ``unprepare_cipher_request``/``unprepare_hash_request``: Called after each
> + request is handled. Clean up / undo what was done in the prepare function.
> +
> +* ``cipher_one_request``/``hash_one_request``: Handle the current request by
> + performing the operation.
I again suggest not using ``<func>`` but instead use <func>()
and remove unnecessary blank lines.
i.e.:
* prepare_crypt_hardware(): Called once before any prepare functions are
called.
* unprepare_crypt_hardware(): Called once after all unprepare functions
have been called.
* prepare_cipher_request()/prepare_hash_request(): Called before each
corresponding request is performed. If some processing or other preparatory
work is required, do it here.
* unprepare_cipher_request()/unprepare_hash_request(): Called after each
request is handled. Clean up / undo what was done in the prepare function.
* cipher_one_request()/hash_one_request(): Handle the current request by
performing the operation.
[]
> +When your driver receives a crypto_request, you must to transfer it to
> +the crypto engine via one of:
> +
> +* crypto_transfer_ablkcipher_request_to_engine()
And removing the unnecessary blank lines below
> +
> +* crypto_transfer_aead_request_to_engine()
> +
> +* crypto_transfer_akcipher_request_to_engine()
> +
> +* crypto_transfer_hash_request_to_engine()
> +
> +* crypto_transfer_skcipher_request_to_engine()
> +
> +At the end of the request process, a call to one of the following functions is needed:
> +
> +* crypto_finalize_ablkcipher_request()
> +
> +* crypto_finalize_aead_request()
> +
> +* crypto_finalize_akcipher_request()
> +
> +* crypto_finalize_hash_request()
> +
> +* crypto_finalize_skcipher_request()
next prev parent reply other threads:[~2019-06-26 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 23:43 [PATCH v2 0/2] Clean up crypto documentation Hook, Gary
2019-06-25 23:43 ` [PATCH v2 1/2] crypto: doc - Add parameter documentation Hook, Gary
2019-06-25 23:43 ` [PATCH v2 2/2] crypto: doc - Fix formatting of new crypto engine content Hook, Gary
2019-06-26 0:13 ` Joe Perches [this message]
2019-06-26 16:50 ` Gary R Hook
2019-07-03 14:28 ` [PATCH v2 0/2] Clean up crypto documentation Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=983486e9b2daaa34f84f99a890fcedfeae22b24f.camel@perches.com \
--to=joe@perches.com \
--cc=Gary.Hook@amd.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox