From: Herbert Xu <herbert@gondor.apana.org.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function
Date: Thu, 12 Dec 2019 14:08:18 +0800 [thread overview]
Message-ID: <20191212060818.w4orbhieq66btymf@gondor.apana.org.au> (raw)
In-Reply-To: <20191211092640.107621-1-Jason@zx2c4.com>
On Wed, Dec 11, 2019 at 10:26:39AM +0100, Jason A. Donenfeld wrote:
> Somehow this was forgotten when Zinc was being split into oddly shaped
> pieces, resulting in linker errors. The x86_64 glue has a specific key
> generation implementation, but the Arm one does not. However, it can
> still receive the NEON speedups by calling the ordinary DH function
> using the base point.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> arch/arm/crypto/curve25519-glue.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Patch 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
prev parent reply other threads:[~2019-12-12 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5def8fc0.1c69fb81.d0c08.f4f4@mx.google.com>
2019-12-10 23:24 ` next/master build: 214 builds: 10 failed, 204 passed, 17 errors, 57 warnings (next-20191210) Stephen Rothwell
2019-12-11 9:26 ` [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function Jason A. Donenfeld
2019-12-11 9:26 ` [PATCH 2/2] crypto: curve25519 - re-add selftests Jason A. Donenfeld
2019-12-11 9:38 ` [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function Ard Biesheuvel
2019-12-11 9:40 ` Jason A. Donenfeld
2019-12-11 12:07 ` Jason A. Donenfeld
2019-12-12 6:08 ` Herbert Xu
2019-12-12 6:08 ` 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=20191212060818.w4orbhieq66btymf@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Jason@zx2c4.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).