From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] lib/crypto: powerpc: Add powerpc/aesp8-ppc.S to clean-files
Date: Tue, 17 Mar 2026 12:10:19 +0100 [thread overview]
Message-ID: <6956f2d9-dd9a-404a-a6e6-1d5478a1410a@app.fastmail.com> (raw)
In-Reply-To: <20260317044925.104184-1-ebiggers@kernel.org>
On Tue, 17 Mar 2026, at 05:49, Eric Biggers wrote:
> Make the generated file powerpc/aesp8-ppc.S be removed by 'make clean'.
>
> Fixes: 7cf2082e74ce ("lib/crypto: powerpc/aes: Migrate POWER8 optimized
> code into library")
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> lib/crypto/Makefile | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
> diff --git a/lib/crypto/Makefile b/lib/crypto/Makefile
> index 725eef05b758..dc7a56f7287d 100644
> --- a/lib/crypto/Makefile
> +++ b/lib/crypto/Makefile
> @@ -53,10 +53,13 @@ endif # CONFIG_PPC
> libaes-$(CONFIG_RISCV) += riscv/aes-riscv64-zvkned.o
> libaes-$(CONFIG_SPARC) += sparc/aes_asm.o
> libaes-$(CONFIG_X86) += x86/aes-aesni.o
> endif # CONFIG_CRYPTO_LIB_AES_ARCH
>
> +# clean-files must be defined unconditionally
> +clean-files += powerpc/aesp8-ppc.S
> +
>
> ################################################################################
>
> obj-$(CONFIG_CRYPTO_LIB_AESCFB) += libaescfb.o
> libaescfb-y := aescfb.o
>
>
> base-commit: ebba09f198078b7a2565004104ef762d1148e7f0
> --
> 2.53.0
next prev parent reply other threads:[~2026-03-17 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 4:49 [PATCH] lib/crypto: powerpc: Add powerpc/aesp8-ppc.S to clean-files Eric Biggers
2026-03-17 11:10 ` Ard Biesheuvel [this message]
2026-03-17 16:28 ` Eric Biggers
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=6956f2d9-dd9a-404a-a6e6-1d5478a1410a@app.fastmail.com \
--to=ardb@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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