From: phil@nwl.cc (Phil Sutter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] [v3] crypto: sha1/ARM: make use of common SHA-1 structures
Date: Tue, 1 Jul 2014 17:29:39 +0200 [thread overview]
Message-ID: <20140701152939.GC8243@orbit.nwl.cc> (raw)
In-Reply-To: <20140630163845.32348.80374.stgit@localhost6.localdomain6>
Hi,
On Mon, Jun 30, 2014 at 07:38:46PM +0300, Jussi Kivilinna wrote:
> Common SHA-1 structures are defined in <crypto/sha.h> for code sharing.
>
> This patch changes SHA-1/ARM glue code to use these structures.
I find it worth noting that this patch also fixes mv_cesa if sha1-arm is
also enabled. This is because software SHA1 is used as fallback,
accessing the context's data which was layed out differently before this
patch.
I have not checked, but other crypto engine drivers might be affected by
that, as well.
> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi>
Acked-by: Phil Sutter <phil@nwl.cc>
Best wishes, Phil
prev parent reply other threads:[~2014-07-01 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 16:38 [PATCH 1/2] [v3] crypto: sha1/ARM: make use of common SHA-1 structures Jussi Kivilinna
2014-06-30 16:38 ` [PATCH 2/2] [v3] crypto: sha1: add ARM NEON implementation Jussi Kivilinna
2014-07-01 15:29 ` Phil Sutter [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=20140701152939.GC8243@orbit.nwl.cc \
--to=phil@nwl.cc \
--cc=linux-arm-kernel@lists.infradead.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).