From: Stephan Mueller <smueller@chronox.de>
To: Marek Vasut <marex@denx.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"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 14:46:41 +0100 [thread overview]
Message-ID: <12522104.5yU5SNjzIg@tachyon.chronox.de> (raw)
In-Reply-To: <201410311009.52713.marex@denx.de>
Am Freitag, 31. Oktober 2014, 10:09:52 schrieb Marek Vasut:
Hi Marek,
> On Friday, October 31, 2014 at 08:23:53 AM, Herbert Xu wrote:
> > On Fri, Oct 31, 2014 at 04:01:04AM +0100, Marek Vasut wrote:
> > > 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.
> >
> > Posting your latest revision would be great.
>
> Please see below, mine is much less complete than Stephan's though
> and likely contains some bugs.
Thank you for sharing.
I am in the last innings to complete a new patch set. I will see to merge your
documentation with mine.
The upcoming patchset will cover the following changes:
- split out the user space interface documentation (and fix a bug -- I forgot
a memset(0) in there)
- keep the "high-level" description in a document in Documentation/crypto/
- put the API function documentation into the header files (I hope that is ok
that I touch these files to add comments)
--
Ciao
Stephan
prev parent reply other threads:[~2014-10-31 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 19:46 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
2014-10-31 7:23 ` Herbert Xu
2014-10-31 9:09 ` Marek Vasut
2014-10-31 13:46 ` Stephan Mueller [this message]
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=12522104.5yU5SNjzIg@tachyon.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 \
--cc=marex@denx.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
all inboxes | Powered by JetHome®