mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
	baolin.wang@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] crypto: engine: permit to enqueue ashash_request
Date: Wed, 7 Sep 2016 21:20:36 +0800	[thread overview]
Message-ID: <20160907132036.GG17176@gondor.apana.org.au> (raw)
In-Reply-To: <1472644978-9003-1-git-send-email-clabbe.montjoie@gmail.com>

On Wed, Aug 31, 2016 at 02:02:56PM +0200, Corentin Labbe wrote:
> Hello
> 
> I wanted to use the crypto engine for my Allwinner crypto driver but something
> prevented me to use it: it cannot enqueue hash requests.
> This patch convert crypto engine to permit enqueuing of ahash_requests.
> It also convert the only driver using crypto engine.
> 
> The modifications against omap was only compile tested but the crypto engine with
> hash support was tested on two different offtree driver (sun4i-ss and sun8i-ce)
> 
> Regards
> 
> Changes since v1:
> - rebased on cryptodev for handling omap-des
> 
> Changes since v2:
> - Fusionned both patch
> - Renamed crypt_one_request to do_one_request
> - Test the type of request before processing it
> 
> Changes sunce v3
> - Add functions for each type (ablkcipher/ahash)
> 
> LABBE Corentin (2):
>   crypto: move crypto engine to its own header
>   crypto: engine: permit to enqueue ashash_request
> 
>  crypto/crypto_engine.c    | 187 ++++++++++++++++++++++++++++++++++++----------
>  drivers/crypto/omap-aes.c |   9 ++-
>  drivers/crypto/omap-des.c |   9 ++-
>  include/crypto/algapi.h   |  70 -----------------
>  include/crypto/engine.h   | 107 ++++++++++++++++++++++++++
>  5 files changed, 266 insertions(+), 116 deletions(-)
>  create mode 100644 include/crypto/engine.h

All applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      parent reply	other threads:[~2016-09-07 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 12:02 Corentin Labbe
2016-08-31 12:02 ` [PATCH v4 1/2] crypto: move crypto engine to its own header Corentin Labbe
2016-08-31 12:02 ` [PATCH v4 2/2] crypto: engine: permit to enqueue ashash_request Corentin Labbe
2016-09-07 13:20 ` Herbert Xu [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=20160907132036.GG17176@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=baolin.wang@linaro.org \
    --cc=clabbe.montjoie@gmail.com \
    --cc=davem@davemloft.net \
    --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®