From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH v3 1/5] cipher: Update for current kernel akcipher interface
Date: Tue, 14 Jun 2016 13:49:37 -0500 [thread overview]
Message-ID: <576051C1.7060606@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1606141031010.13500@animeshb-mobl.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Hi Mat,
>
> Having the pending data check is one part of clarifying the semantics,
> and I agree that docs are important for this. I'll check up on the
> documentation side of things (Stephan usually includes docs, but they're
> missing from akcipher).
>
Go ahead and make a judgement call. If you think that 1 socket is
enough / what the kernel intends, then I'm fine taking such a patch.
Regards,
-Denis
prev parent reply other threads:[~2016-06-14 18:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 17:09 [PATCH v3 1/5] cipher: Update for current kernel akcipher interface Mat Martineau
2016-06-10 17:09 ` [PATCH v3 2/5] unit: Update for akcipher changes Mat Martineau
2016-06-10 17:09 ` [PATCH v3 3/5] cipher: Return result length from asymmetric cipher Mat Martineau
2016-06-13 20:59 ` Mat Martineau
2016-06-10 17:09 ` [PATCH v3 4/5] unit: Check asymmetric cipher result lengths Mat Martineau
2016-06-10 17:09 ` [PATCH v3 5/5] unit: Check decryption against known ciphertext Mat Martineau
2016-06-13 17:49 ` [PATCH v3 1/5] cipher: Update for current kernel akcipher interface Denis Kenzior
2016-06-13 20:56 ` Mat Martineau
2016-06-13 21:13 ` Denis Kenzior
2016-06-13 22:29 ` Mat Martineau
2016-06-13 22:51 ` Denis Kenzior
2016-06-14 17:37 ` Mat Martineau
2016-06-14 18:49 ` Denis Kenzior [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=576051C1.7060606@gmail.com \
--to=denkenz@gmail.com \
--cc=ell@lists.01.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.