From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] crypto: niagara: Use precalculated hash from headers
Date: Thu, 17 Dec 2015 09:48:24 +0100 [thread overview]
Message-ID: <20151217084824.GA20217@Red> (raw)
In-Reply-To: <20151217084018.GA9166@gondor.apana.org.au>
On Thu, Dec 17, 2015 at 04:40:18PM +0800, Herbert Xu wrote:
> On Tue, Dec 15, 2015 at 02:00:21PM +0100, LABBE Corentin wrote:
> > Precalculated hash for empty message are now present in hash headers.
> > This patch just use them.
> >
> > Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
> > ---
> > drivers/crypto/Kconfig | 2 ++
> > drivers/crypto/n2_core.c | 33 ++++++---------------------------
> > 2 files changed, 8 insertions(+), 27 deletions(-)
> >
> > diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
> > index b9ec295..dea754b 100644
> > --- a/drivers/crypto/Kconfig
> > +++ b/drivers/crypto/Kconfig
> > @@ -194,6 +194,8 @@ config CRYPTO_DEV_NIAGARA2
> > select CRYPTO_DES
> > select CRYPTO_BLKCIPHER
> > select CRYPTO_HASH
> > + select CRYPTO_MD5
> > + select CRYPTO_SHA1
>
> Don't we need CRYPTO_SHA256 as well?
>
> Thanks,
Hello
You are right, I missed it also in ccp/ux500.
Regards
next prev parent reply other threads:[~2015-12-17 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 13:00 [PATCH v3 0/4] crypto: add precalculated hash for zero message length LABBE Corentin
2015-12-15 13:00 ` [PATCH v3 1/4] crypto: hash: add zero length message hash for shax and md5 LABBE Corentin
2015-12-15 13:00 ` [PATCH v3 2/4] crypto: niagara: Use precalculated hash from headers LABBE Corentin
2015-12-17 8:40 ` Herbert Xu
2015-12-17 8:48 ` LABBE Corentin [this message]
2015-12-17 8:51 ` Herbert Xu
2015-12-15 13:00 ` [PATCH v3 3/4] crypto: ccp: " LABBE Corentin
2015-12-15 13:00 ` [PATCH v3 4/4] crypto: ux500: " LABBE Corentin
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=20151217084824.GA20217@Red \
--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