| Message ID | 20230117144747.37115c52@canb.auug.org.au (mailing list archive) |
|---|---|
| State | Not Applicable |
| Delegated to: | Herbert Xu |
| Headers | show |
| Series | linux-next: build failure after merge of the crypto tree | expand |
diff --git a/arch/powerpc/crypto/Kconfig b/arch/powerpc/crypto/Kconfig index db7d99383993..36928ad14a6b 100644 --- a/arch/powerpc/crypto/Kconfig +++ b/arch/powerpc/crypto/Kconfig @@ -97,6 +97,7 @@ config CRYPTO_AES_PPC_SPE config CRYPTO_P10_AES_GCM tristate "Stitched AES/GCM acceleration support on P10+ CPU (PPC)" depends on PPC64 + depends on PPC64_ELF_ABI_V1 select CRYPTO_LIB_AES select CRYPTO_ALGAPI select CRYPTO_AEAD
Hi all, After merging the crypto tree, today's linux-next build (powerpc pseries_le_defconfig) failed like this: arch/powerpc/crypto/p10_aes_gcm.o: warning: objtool: .text+0x884: unannotated intra-function call arch/powerpc/crypto/aesp8-ppc.o: warning: objtool: aes_p8_set_encrypt_key+0x44: unannotated intra-function call ld: arch/powerpc/crypto/p10_aes_gcm.o: ABI version 1 is not compatible with ABI version 2 output ld: failed to merge target specific data of file arch/powerpc/crypto/p10_aes_gcm.o Caused by commit ca68a96c37eb ("crypto: p10-aes-gcm - An accelerated AES/GCM stitched implementation") I have applied the following hack for today. From: Stephen Rothwell <sfr@canb.auug.org.au> Date: Tue, 17 Jan 2023 14:41:10 +1100 Subject: [PATCH] crypto: p10-aes-gcm - only ABIv1 code has been implemented Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au> --- arch/powerpc/crypto/Kconfig | 1 + 1 file changed, 1 insertion(+)