Skip to content

arm64: Make extension enablement consistent

Mark Brown linux-arm-kernel linux-crypto 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2arm64: crypto: Consistently enable extensionarch/arm64/crypto/crct10dif-ce-core.S+1 -10 replies
2/2arm64: lib: Consistently enable crc32 extensionarch/arm64/lib/crc32.S+1 -10 replies

Reviews trailers per patch

None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchArd Biesheuvel
SeriesA-b
1/2
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] arm64: Make extension enablement consistent

Currently we use a mix of .arch and .cpu to enable architecture extensions, make things consistent by converting the two instances of .cpu to .arch which is more common and a bit more idiomatic for our goal.

Mark Brown (2):
arm64: crypto: Consistently enable extension
arm64: lib: Consistently enable crc32 extension

 arch/arm64/crypto/crct10dif-ce-core.S | 2 +-
 arch/arm64/lib/crc32.S                | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
Signature · 1 line
2.20.1