From: Masahiro Yamada <masahiroy@kernel•org>
To: Herbert Xu <herbert@gondor•apana.org.au>,
"David S . Miller" <davem@davemloft•net>,
linux-crypto@vger•kernel.org
Cc: "kernel test robot" <lkp@intel•com>,
"Masahiro Yamada" <masahiroy@kernel•org>,
"Nayna Jain" <nayna@linux•ibm.com>,
linux-kernel@vger•kernel.org, "Paul Mackerras" <paulus@samba•org>,
"Breno Leitão" <leitao@debian•org>,
"Paulo Flabiano Smorigo" <pfsmorigo@gmail•com>,
linuxppc-dev@lists•ozlabs.org
Subject: [PATCH] crypto: vmx - Fix build error
Date: Sat, 7 May 2022 14:22:43 +0900 [thread overview]
Message-ID: <20220507052244.1426765-1-masahiroy@kernel.org> (raw)
When I refactored this Makefile, I accidentally changed the CONFIG
option.
Fixes: b52455a73db9 ("crypto: vmx - Align the short log with Makefile cleanups")
Reported-by: kernel test robot <lkp@intel•com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel•org>
---
drivers/crypto/vmx/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/vmx/Makefile b/drivers/crypto/vmx/Makefile
index df93ba63b1cd..2560cfea1dec 100644
--- a/drivers/crypto/vmx/Makefile
+++ b/drivers/crypto/vmx/Makefile
@@ -3,7 +3,7 @@ obj-$(CONFIG_CRYPTO_DEV_VMX_ENCRYPT) += vmx-crypto.o
vmx-crypto-objs := vmx.o aesp8-ppc.o ghashp8-ppc.o aes.o aes_cbc.o aes_ctr.o aes_xts.o ghash.o
quiet_cmd_perl = PERL $@
- cmd_perl = $(PERL) $< $(if $(CONFIG_LITTLE_ENDIAN), linux-ppc64le, linux-ppc64) > $@
+ cmd_perl = $(PERL) $< $(if $(CONFIG_CPU_LITTLE_ENDIAN), linux-ppc64le, linux-ppc64) > $@
targets += aesp8-ppc.S ghashp8-ppc.S
--
2.32.0
next reply other threads:[~2022-05-07 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 5:22 Masahiro Yamada [this message]
2022-05-10 3:21 ` [PATCH] crypto: vmx - Fix build error 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=20220507052244.1426765-1-masahiroy@kernel.org \
--to=masahiroy@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=leitao@debian$(echo .)org \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=lkp@intel$(echo .)com \
--cc=nayna@linux$(echo .)ibm.com \
--cc=paulus@samba$(echo .)org \
--cc=pfsmorigo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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