From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: [PATCH 0/3 v3] crypto: engine - Permit to enqueue skcipher request
Date: Mon, 14 Aug 2017 15:17:22 +0200 [thread overview]
Message-ID: <20170814131725.9402-1-clabbe.montjoie@gmail.com> (raw)
Hello
The crypto engine could actually only enqueue hash and ablkcipher request.
This patch serie permit it to enqueue skcipher requests by adding all necessary
functions.
Changes since v2
- added two patch for finding request type according to its cra_type
Changes since v1
- Aligned to column struct *dev in include
- Added missing mutex_unlock in crypto_engine_start()
Corentin Labbe (3):
crypto: skcipher - export crypto_skcipher_type2
crypto: engine - find request type with cra_type
crypto: engine - Permit to enqueue skcipher request
crypto/crypto_engine.c | 133 ++++++++++++++++++++++++++++++++++++++++++++----
crypto/skcipher.c | 3 +-
include/crypto/algapi.h | 1 +
include/crypto/engine.h | 14 +++++
4 files changed, 139 insertions(+), 12 deletions(-)
--
2.13.0
next reply other threads:[~2017-08-14 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 13:17 Corentin Labbe [this message]
2017-08-14 13:17 ` [PATCH 1/3] crypto: skcipher - export crypto_skcipher_type2 Corentin Labbe
2017-08-14 13:17 ` [PATCH 2/3] crypto: engine - find request type with cra_type Corentin Labbe
2017-08-15 7:51 ` Fabien DESSENNE
2017-08-16 8:58 ` Corentin Labbe
2017-08-18 8:28 ` Herbert Xu
2017-08-18 11:40 ` Corentin Labbe
2017-08-14 13:17 ` [PATCH 3/3] crypto: engine - Permit to enqueue skcipher request Corentin Labbe
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=20170814131725.9402-1-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--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
all inboxes | Powered by JetHome®