mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v2 0/2] crypto: engine - Permit to enqueue skcipher request
Date: Tue,  6 Jun 2017 15:44:15 +0200	[thread overview]
Message-ID: <20170606134417.18850-1-clabbe.montjoie@gmail.com> (raw)

The crypto engine could actually only enqueue hash and ablkcipher request.
This patch serie permit it to enqueue skcipher requets by adding all necessary
functions.

Changes since v1
- Aligned to column struct *dev in include
- Added missing mutex_unlock in crypto_engine_start()

Corentin Labbe (2):
  crypto: engine - replace pr_xxx by dev_xxx
  crypto: engine - Permit to enqueue skcipher request

 crypto/crypto_engine.c  | 157 ++++++++++++++++++++++++++++++++++++++++++------
 include/crypto/engine.h |  15 +++++
 2 files changed, 153 insertions(+), 19 deletions(-)

-- 
2.13.0

             reply	other threads:[~2017-06-06 13:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 13:44 Corentin Labbe [this message]
2017-06-06 13:44 ` [PATCH v2 1/2] crypto: engine - replace pr_xxx by dev_xxx Corentin Labbe
2017-06-19  6:46   ` Herbert Xu
2017-06-06 13:44 ` [PATCH v2 2/2] crypto: engine - Permit to enqueue skcipher request Corentin Labbe
2017-06-06 14:07   ` Stephan Müller
2017-06-06 14:24     ` Corentin Labbe
2017-06-19  5:27   ` Herbert Xu
2017-06-19  7:55     ` Corentin Labbe
2017-06-23  6:48       ` Herbert Xu
2017-07-14 11:15         ` Corentin Labbe
2017-07-28 13:52           ` Herbert Xu
2017-07-28 15:01             ` Corentin Labbe
2017-08-09  9:40               ` Corentin Labbe
2017-08-21 15:07                 ` Herbert Xu

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=20170606134417.18850-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®