From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel crypto API interface specification
Date: Tue, 14 Oct 2014 22:00:37 +0200 [thread overview]
Message-ID: <2178720.yAoRcDWDgu@myon.chronox.de> (raw)
In-Reply-To: <7502136.9BkWHTZ0th@myon.chronox.de>
Am Dienstag, 14. Oktober 2014, 21:46:50 schrieb Stephan Mueller:
Hi,
> The update adds a complete interface documentation of the kernel crypto
> API. All cipher types supported by the kernel crypto API are documented.
>
> In addition, kernel and user space example code is provided. The sample
> code covers synchronous and asynchronous cipher operation, random
> number generation and performing hashing as well as encryption and
> decryption in user space.
I was not sure whether to cover the explanation of the API in a separate
document or whether to add the function documentation to
include/linux/crypto.h.
With the first attempt of the documentation, I applied the least invasive
approach. If it is requested, I would modify the patch such that appropriate
source code comments to the functions in the header file are added.
--
Ciao
Stephan
next prev parent reply other threads:[~2014-10-14 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 19:46 [PATCH] kernel crypto API interface specification Stephan Mueller
2014-10-14 20:00 ` Stephan Mueller [this message]
2014-10-15 17:58 ` Jason Cooper
2014-10-16 7:19 ` Stephan Mueller
2014-10-16 13:25 ` Jason Cooper
2014-10-16 13:29 ` Jason Cooper
2014-10-16 15:06 ` Jason Cooper
2014-10-16 16:50 ` Stephan Mueller
2014-10-16 17:42 ` Jason Cooper
2014-10-16 13:10 ` Herbert Xu
2014-10-31 3:01 ` Marek Vasut
2014-10-31 7:23 ` Herbert Xu
2014-10-31 9:09 ` Marek Vasut
2014-10-31 13:46 ` 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=2178720.yAoRcDWDgu@myon.chronox.de \
--to=smueller@chronox.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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