From: Eric Biggers <ebiggers@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-crypto@vger.kernel.org, Samuel Neves <sneves@dei.uc.pt>,
Andy Polyakov <appro@openssl.org>
Subject: Re: [PATCH crypto-next v5 2/3] crypto: x86_64/poly1305 - add faster implementations
Date: Sun, 15 Dec 2019 22:00:26 -0800 [thread overview]
Message-ID: <20191216060026.GC908@sol.localdomain> (raw)
In-Reply-To: <20191215204631.142024-3-Jason@zx2c4.com>
On Sun, Dec 15, 2019 at 09:46:30PM +0100, Jason A. Donenfeld wrote:
> diff --git a/arch/x86/crypto/Makefile b/arch/x86/crypto/Makefile
> index 958440eae27e..6982a2f8863f 100644
> --- a/arch/x86/crypto/Makefile
> +++ b/arch/x86/crypto/Makefile
> @@ -73,6 +73,10 @@ aegis128-aesni-y := aegis128-aesni-asm.o aegis128-aesni-glue.o
>
> nhpoly1305-sse2-y := nh-sse2-x86_64.o nhpoly1305-sse2-glue.o
> blake2s-x86_64-y := blake2s-core.o blake2s-glue.o
> +poly1305-x86_64-y := poly1305-x86_64.o poly1305_glue.o
> +ifneq ($(CONFIG_CRYPTO_POLY1305_X86_64),)
> +targets += poly1305-x86_64.S
> +endif
poly1305-x86_64.S is a generated file, so it needs to be listed in a gitignore
file arch/x86/crypto/.gitignore.
- Eric
next prev parent reply other threads:[~2019-12-16 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 20:46 [PATCH crypto-next v5 0/3] crypto: poly1305 improvements Jason A. Donenfeld
2019-12-15 20:46 ` [PATCH crypto-next v5 1/3] crypto: poly1305 - add new 32 and 64-bit generic versions Jason A. Donenfeld
2019-12-15 20:46 ` [PATCH crypto-next v5 2/3] crypto: x86_64/poly1305 - add faster implementations Jason A. Donenfeld
2019-12-16 6:00 ` Eric Biggers [this message]
2019-12-16 9:49 ` Jason A. Donenfeld
2019-12-15 20:46 ` [PATCH crypto-next v5 3/3] crypto: arm/arm64/mips/poly1305 - remove redundant non-reduction from emit Jason A. Donenfeld
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=20191216060026.GC908@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=appro@openssl.org \
--cc=linux-crypto@vger.kernel.org \
--cc=sneves@dei.uc.pt \
/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