From: Marek Vasut <marex@denx.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Stephan Mueller <smueller@chronox.de>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel crypto API interface specification
Date: Fri, 31 Oct 2014 04:01:04 +0100 [thread overview]
Message-ID: <201410310401.04278.marex@denx.de> (raw)
In-Reply-To: <20141016131007.GA11517@gondor.apana.org.au>
On Thursday, October 16, 2014 at 03:10:07 PM, Herbert Xu wrote:
> On Tue, Oct 14, 2014 at 09:46:50PM +0200, Stephan Mueller wrote:
> > 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.
> >
> > Signed-off-by: Stephan Mueller <smueller@chronox.de>
>
> Thanks for the patch Stephan!
>
> Marek Vasut <marex@denx.de> has also been working on a set of
> documentation for the crypto API so he might have some comments
> on this.
Sorry for the late reply, thanks for keeping me in the loop.
I can share the last state of the document I wrote. Currently,
it is not possible for me to keep up with my workload and do
anything else, so that's all I can do.
Apologies.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-31 3:09 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
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 [this message]
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=201410310401.04278.marex@denx.de \
--to=marex@denx.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/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