From: Stephan Mueller <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH 4/7] crypto: doc - fix separation of cipher / req API
Date: Sun, 16 Oct 2016 05:18:48 +0200 [thread overview]
Message-ID: <5908263.2TLWr89bHl@positron.chronox.de> (raw)
In-Reply-To: <2721226.4nLlHD9uQ6@positron.chronox.de>
Keep the cipher API and the request API function documentation in
separate sections.
Signed-off-by: Stephan Mueller <smueller@chronox.de>
---
Documentation/crypto/api-akcipher.rst | 25 +++++++++++++------------
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/Documentation/crypto/api-akcipher.rst b/Documentation/crypto/api-akcipher.rst
index 305e616..0d5899f 100644
--- a/Documentation/crypto/api-akcipher.rst
+++ b/Documentation/crypto/api-akcipher.rst
@@ -25,32 +25,32 @@ Asymmetric Cipher API
.. kernel-doc:: include/crypto/akcipher.h
:functions: crypto_akcipher_set_priv_key
-Asymmetric Cipher Request Handle
---------------------------------
-
.. kernel-doc:: include/crypto/akcipher.h
- :functions: akcipher_request_alloc
+ :functions: crypto_akcipher_maxsize
.. kernel-doc:: include/crypto/akcipher.h
- :functions: akcipher_request_free
+ :functions: crypto_akcipher_encrypt
.. kernel-doc:: include/crypto/akcipher.h
- :functions: akcipher_request_set_callback
+ :functions: crypto_akcipher_decrypt
.. kernel-doc:: include/crypto/akcipher.h
- :functions: akcipher_request_set_crypt
+ :functions: crypto_akcipher_sign
.. kernel-doc:: include/crypto/akcipher.h
- :functions: crypto_akcipher_maxsize
+ :functions: crypto_akcipher_verify
+
+Asymmetric Cipher Request Handle
+--------------------------------
.. kernel-doc:: include/crypto/akcipher.h
- :functions: crypto_akcipher_encrypt
+ :functions: akcipher_request_alloc
.. kernel-doc:: include/crypto/akcipher.h
- :functions: crypto_akcipher_decrypt
+ :functions: akcipher_request_free
.. kernel-doc:: include/crypto/akcipher.h
- :functions: crypto_akcipher_sign
+ :functions: akcipher_request_set_callback
.. kernel-doc:: include/crypto/akcipher.h
- :functions: crypto_akcipher_verify
+ :functions: akcipher_request_set_crypt
--
2.7.4
next prev parent reply other threads:[~2016-10-16 3:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 3:15 [PATCH 0/7] Conversion crypto API documentation to Sphinx Stephan Mueller
2016-10-16 3:16 ` [PATCH 1/7] crypto: doc - convert " Stephan Mueller
2016-10-16 3:17 ` [PATCH 2/7] crypto: doc - remove crypto API DocBook Stephan Mueller
2016-10-16 3:18 ` [PATCH 3/7] crypto: doc - fix source comments for Sphinx Stephan Mueller
2016-10-16 12:56 ` Markus Heiser
2016-10-16 13:03 ` Stephan Mueller
2016-10-16 13:42 ` Markus Heiser
2016-10-16 3:18 ` Stephan Mueller [this message]
2016-10-17 11:04 ` [PATCH 4/7] crypto: doc - fix separation of cipher / req API Jani Nikula
2016-10-17 12:35 ` Stephan Mueller
2016-10-17 13:20 ` Jani Nikula
2016-10-16 3:19 ` [PATCH 5/7] crypto: doc - add KPP documentation Stephan Mueller
2016-10-16 3:19 ` [PATCH 6/7] crypto: doc - remove crypto_alloc_ablkcipher Stephan Mueller
2016-10-16 3:22 ` [PATCH 7/7] crypto: doc - clarify AEAD memory structure Stephan Mueller
2016-10-16 13:11 ` Markus Heiser
2016-10-16 13:20 ` Stephan Mueller
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=5908263.2TLWr89bHl@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.