From: Christophe LEROY <christophe.leroy@c-s.fr>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/6] crypto: talitos - various fixes
Date: Wed, 20 Sep 2017 10:35:41 +0200 [thread overview]
Message-ID: <d1a928d5-d5cd-baf6-a6bf-2375cce4b4a4@c-s.fr> (raw)
In-Reply-To: <cover.1505825623.git.christophe.leroy@c-s.fr>
Looks like the linux-crypto list and patchwork was out of order when I
sent this. I will send again, sorry for the noise on the other lists.
Le 19/09/2017 à 14:58, Christophe Leroy a écrit :
> This serie provide various fixes on the talitos driver.
>
> Christophe Leroy (6):
> crypto: talitos - Don't provide setkey for non hmac hashing algs.
> crypto: talitos - fix hashing
> crypto: talitos - fix sha224
> crypto: talitos - fix AEAD test failures
> crypto: talitos - use kzalloc instead of kmalloc
> crypto: talitos - fix memory corruption on SEC2
>
> drivers/crypto/talitos.c | 81 +++++++++++++++++++++---------------------------
> drivers/crypto/talitos.h | 2 --
> 2 files changed, 36 insertions(+), 47 deletions(-)
>
next prev parent reply other threads:[~2017-09-20 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 12:58 [PATCH 0/6] crypto: talitos - various fixes Christophe Leroy
2017-09-19 12:59 ` [PATCH 1/6] crypto: talitos - Don't provide setkey for non hmac hashing algs Christophe Leroy
2017-09-19 12:59 ` [PATCH 2/6] crypto: talitos - fix hashing Christophe Leroy
2017-09-19 12:59 ` [PATCH 3/6] crypto: talitos - fix sha224 Christophe Leroy
2017-09-19 12:59 ` [PATCH 4/6] crypto: talitos - fix AEAD test failures Christophe Leroy
2017-09-19 12:59 ` [PATCH 5/6] crypto: talitos - use kzalloc instead of kmalloc Christophe Leroy
2017-09-19 12:59 ` [PATCH 6/6] crypto: talitos - fix memory corruption on SEC2 Christophe Leroy
2017-09-20 8:35 ` Christophe LEROY [this message]
2017-09-20 19:21 ` [PATCH 0/6] crypto: talitos - various fixes christophe leroy
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=d1a928d5-d5cd-baf6-a6bf-2375cce4b4a4@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).