From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function
Date: Wed, 11 Dec 2019 13:07:43 +0100 [thread overview]
Message-ID: <CAHmME9r09=YNw1MmnzoRLA4szJ9zz-uV4Hut4dFZKHDwG8Qp6A@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu80vONMAuv=2OpSOuZHvVv22quRxeNtbxnSkFBz_DvfbQ@mail.gmail.com>
On Wed, Dec 11, 2019 at 10:38 AM Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> > 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>
>
> With the first sentence dropped,
>
> Acked-by: Ard Biesheuvel <ardb@kernel.org>
Herbert - can you pick this up for 5.5-rc2 rather than 5.6?
next prev parent reply other threads:[~2019-12-11 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191211102455.7b55218e@canb.auug.org.au>
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 [this message]
2019-12-12 6:08 ` Herbert Xu
2019-12-12 6:08 ` Herbert Xu
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='CAHmME9r09=YNw1MmnzoRLA4szJ9zz-uV4Hut4dFZKHDwG8Qp6A@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=ard.biesheuvel@linaro.org \
--cc=herbert@gondor.apana.org.au \
--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).