From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Andy Polyakov <appro@cryptogams.org>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
George Cherian <gcherian@marvell.com>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] crypto: mips/poly1305 - enable for all MIPS processors
Date: Wed, 3 Mar 2021 13:32:43 +0100 [thread overview]
Message-ID: <CAHmME9omx45G_UtnTnyt7LFr70Uou0JM8vboF-C=ZdD1ttBQoQ@mail.gmail.com> (raw)
In-Reply-To: <70eb96e1-3243-105c-b52e-c9bd3239a263@cryptogams.org>
On Wed, Mar 3, 2021 at 1:31 PM Andy Polyakov <appro@cryptogams.org> wrote:
>
> Hi,
>
> > I'm also CC'ing Andy on this, who wrote the original assembly, in case
> > he has some last minute objection.
>
> Just "what took you so long":-) On potentially related note cryptogams
> chacha-mips is as universal as poly1305-mips. "Universal" in sense that
> it can be compiled for all MIPS stripes.
Oh great. I didn't realize you had a ChaCha mips implementation. I'll
look into having that replace my junky mips32r2 one.
Jason
next prev parent reply other threads:[~2021-03-03 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 1:16 [PATCH] crypto: mips/poly1305 - enable for all MIPS processors Maciej W. Rozycki
2021-03-03 8:17 ` Jason A. Donenfeld
2021-03-03 12:31 ` Andy Polyakov
2021-03-03 12:32 ` Jason A. Donenfeld [this message]
2021-03-08 10:54 ` Thomas Bogendoerfer
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='CAHmME9omx45G_UtnTnyt7LFr70Uou0JM8vboF-C=ZdD1ttBQoQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=appro@cryptogams.org \
--cc=chenhuacai@kernel.org \
--cc=gcherian@marvell.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=ralf@linux-mips.org \
--cc=stable@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).