From: Maxime Ripard <maxime@cerno.tech>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
mark.rutland@arm.com, mripard@kernel.org, robh+dt@kernel.org,
wens@csie.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH v2 3/3] crypto: sun4i-ss: add the A33 variant of SS
Date: Fri, 22 Nov 2019 13:53:09 +0100 [thread overview]
Message-ID: <20191122125309.GL4345@gilmour.lan> (raw)
In-Reply-To: <20191120152833.20443-4-clabbe.montjoie@gmail.com>
On Wed, Nov 20, 2019 at 04:28:33PM +0100, Corentin Labbe wrote:
> The A33 SS has a difference with all other SS, it give SHA1 digest
> directly in BE.
> So this patch adds variant support in sun4i-ss.
>
> Fixes: 6298e948215f ("crypto: sunxi-ss - Add Allwinner Security System crypto accelerator")
> Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
Acked-by: Maxime Ripard <mripard@kernel.org>
I'll apply the DT patches once Herbert will have merged this patch.
Thanks!
Maxime
next prev parent reply other threads:[~2019-11-22 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 15:28 [PATCH v2 0/3] crypto: sun4i-ss: fix SHA1 on A33 SecuritySystem Corentin Labbe
2019-11-20 15:28 ` [PATCH v2 1/3] dt-bindings: crypto: add new compatible for A33 SS Corentin Labbe
2019-12-04 16:18 ` Rob Herring
2019-11-20 15:28 ` [PATCH v2 2/3] ARM: dts: sun8i: a33: add the new SS compatible Corentin Labbe
2019-11-20 15:28 ` [PATCH v2 3/3] crypto: sun4i-ss: add the A33 variant of SS Corentin Labbe
2019-11-22 12:53 ` Maxime Ripard [this message]
2019-12-11 9:35 ` Herbert Xu
2020-03-12 5:39 ` [linux-sunxi] [PATCH v2 0/3] crypto: sun4i-ss: fix SHA1 on A33 SecuritySystem Chen-Yu Tsai
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=20191122125309.GL4345@gilmour.lan \
--to=maxime@cerno.tech \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).