From: Mark Brown <broonie@kernel.org> To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Eric Biggers <ebiggers@google.com>, Ard Biesheuvel <ardb@kernel.org> Cc: linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, Mark Brown <broonie@kernel.org> Subject: [PATCH 2/2] arm64: lib: Consistently enable crc32 extension Date: Wed, 25 Mar 2020 13:55:22 +0000 [thread overview] Message-ID: <20200325135522.7782-3-broonie@kernel.org> (raw) In-Reply-To: <20200325135522.7782-1-broonie@kernel.org> Currently most of the assembly files that use architecture extensions enable them using the .arch directive but crc32.S uses .cpu instead. Move that over to .arch for consistency. Signed-off-by: Mark Brown <broonie@kernel.org> --- arch/arm64/lib/crc32.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/lib/crc32.S b/arch/arm64/lib/crc32.S index 243e107e9896..0f9e10ecda23 100644 --- a/arch/arm64/lib/crc32.S +++ b/arch/arm64/lib/crc32.S @@ -9,7 +9,7 @@ #include <asm/alternative.h> #include <asm/assembler.h> - .cpu generic+crc + .arch armv8-a+crc .macro __crc32, c cmp x2, #16 -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Eric Biggers <ebiggers@google.com>, Ard Biesheuvel <ardb@kernel.org> Cc: Mark Brown <broonie@kernel.org>, linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/2] arm64: lib: Consistently enable crc32 extension Date: Wed, 25 Mar 2020 13:55:22 +0000 [thread overview] Message-ID: <20200325135522.7782-3-broonie@kernel.org> (raw) In-Reply-To: <20200325135522.7782-1-broonie@kernel.org> Currently most of the assembly files that use architecture extensions enable them using the .arch directive but crc32.S uses .cpu instead. Move that over to .arch for consistency. Signed-off-by: Mark Brown <broonie@kernel.org> --- arch/arm64/lib/crc32.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/lib/crc32.S b/arch/arm64/lib/crc32.S index 243e107e9896..0f9e10ecda23 100644 --- a/arch/arm64/lib/crc32.S +++ b/arch/arm64/lib/crc32.S @@ -9,7 +9,7 @@ #include <asm/alternative.h> #include <asm/assembler.h> - .cpu generic+crc + .arch armv8-a+crc .macro __crc32, c cmp x2, #16 -- 2.20.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-25 13:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-25 13:55 [PATCH 0/2] arm64: Make extension enablement consistent Mark Brown 2020-03-25 13:55 ` Mark Brown 2020-03-25 13:55 ` [PATCH 1/2] arm64: crypto: Consistently enable extension Mark Brown 2020-03-25 13:55 ` Mark Brown 2020-03-25 13:55 ` Mark Brown [this message] 2020-03-25 13:55 ` [PATCH 2/2] arm64: lib: Consistently enable crc32 extension Mark Brown 2020-03-25 16:00 ` [PATCH 0/2] arm64: Make extension enablement consistent Ard Biesheuvel 2020-03-25 16:00 ` Ard Biesheuvel
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=20200325135522.7782-3-broonie@kernel.org \ --to=broonie@kernel.org \ --cc=ardb@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=ebiggers@google.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-crypto@vger.kernel.org \ --cc=will@kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.