Changes in Makefile

c17ee635fd3a482b2ad2bf5e269755c2eae5f25e - Merge drm/drm-fixes into drm-misc-fixes

Mon, 23 Feb 2026 09:09:45 +0000

Merge drm/drm-fixes into drm-misc-fixes7.0-rc1 was just released, let's merge it to kick the new release cycle.Signed-off-by: Maxime Ripard List of files: /linux/arch/x86/crypto/Makefile

a4a508df2aa34f8650afde54ea804321c618f45f - Merge tag 'v6.18' into next

Sat, 13 Dec 2025 09:18:20 +0000

Merge tag 'v6.18' into nextSync up with the mainline to bring in the latest APIs. List of files: /linux/arch/x86/crypto/Makefile

cc4adab164b772a34b3340d644b7c4728498581e - Merge tag 'v6.19-rc1' into msm-next

Tue, 20 Jan 2026 22:06:55 +0000

Merge tag 'v6.19-rc1' into msm-nextMerge Linux 6.19-rc1 in order to catch up with other changes (e.g. UBWCconfig database defining UBWC_6).Signed-off-by: Dmitry Baryshkov List of files: /linux/arch/x86/crypto/Makefile

5add3c3c280a35f7e258e9cef7607db5a2e56fdc - Merge drm/drm-next into drm-xe-next

Fri, 19 Dec 2025 10:51:22 +0000

Merge drm/drm-next into drm-xe-nextBackmerging to bring in 6.19-rc1. An important upstream bugfix andto help unblock PTL CI.Signed-off-by: Thomas Hellström List of files: /linux/arch/x86/crypto/Makefile

b8304863a3990d0f18c38e5b94191830a63ee1af - Merge drm/drm-next into drm-intel-next

Mon, 15 Dec 2025 13:24:02 +0000

Merge drm/drm-next into drm-intel-nextSync-up some display code needed for Async flips refactor.Signed-off-by: Rodrigo Vivi List of files: /linux/arch/x86/crypto/Makefile

7f790dd21a931c61167f7bdc327aecf2cebad327 - Merge drm/drm-next into drm-misc-next

Mon, 15 Dec 2025 08:27:39 +0000

Merge drm/drm-next into drm-misc-nextLet's kickstart the v6.20 (7.0?) release cycle.Signed-off-by: Maxime Ripard List of files: /linux/arch/x86/crypto/Makefile

13d83ea9d81ddcb08b46377dcc9de6e5df1248d1 - Merge tag 'libcrypto-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux

Tue, 10 Feb 2026 16:31:09 +0000

Merge tag 'libcrypto-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linuxPull crypto library updates from Eric Biggers: - Add support for verifying ML-DSA signatures. ML-DSA (Module-Lattice-Based Digital Signature Algorithm) is a recently-standardized post-quantum (quantum-resistant) signature algorithm. It was known as Dilithium pre-standardization. The first use case in the kernel will be module signing. But there are also other users of RSA and ECDSA signatures in the kernel that might want to upgrade to ML-DSA eventually. - Improve the AES library: - Make the AES key expansion and single block encryption and decryption functions use the architecture-optimized AES code. Enable these optimizations by default. - Support preparing an AES key for encryption-only, using about half as much memory as a bidirectional key. - Replace the existing two generic implementations of AES with a single one. - Simplify how Adiantum message hashing is implemented. Remove the "nhpoly1305" crypto_shash in favor of direct lib/crypto/ support for NH hashing, and enable optimizations by default.* tag 'libcrypto-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux: (53 commits) lib/crypto: mldsa: Clarify the documentation for mldsa_verify() slightly lib/crypto: aes: Drop 'volatile' from aes_sbox and aes_inv_sbox lib/crypto: aes: Remove old AES en/decryption functions lib/crypto: aesgcm: Use new AES library API lib/crypto: aescfb: Use new AES library API crypto: omap - Use new AES library API crypto: inside-secure - Use new AES library API crypto: drbg - Use new AES library API crypto: crypto4xx - Use new AES library API crypto: chelsio - Use new AES library API crypto: ccp - Use new AES library API crypto: x86/aes-gcm - Use new AES library API crypto: arm64/ghash - Use new AES library API crypto: arm/ghash - Use new AES library API staging: rtl8723bs: core: Use new AES library API net: phy: mscc: macsec: Use new AES library API chelsio: Use new AES library API Bluetooth: SMP: Use new AES library API crypto: x86/aes - Remove the superseded AES-NI crypto_cipher lib/crypto: x86/aes: Add AES-NI optimization ... List of files: /linux/arch/x86/crypto/Makefile

a229d83235c7627c490deb7dd4744a72567cea12 - lib/crypto: x86/nh: Migrate optimized code into library

Thu, 11 Dec 2025 01:18:37 +0000

lib/crypto: x86/nh: Migrate optimized code into libraryMigrate the x86_64 implementations of NH into lib/crypto/. This makesthe nh() function be optimized on x86_64 kernels.Note: this temporarily makes the adiantum template not utilize thex86_64 optimized NH code. This is resolved in a later commit thatconverts the adiantum template to use nh() instead of "nhpoly1305".Link: https://lore.kernel.org/r/20251211011846.8179-6-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/x86/crypto/Makefile

24f171c7e145f43b9f187578e89b0982ce87e54c - Merge tag 'asoc-fix-v6.19-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Sun, 21 Dec 2025 10:11:11 +0000

Merge tag 'asoc-fix-v6.19-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Fixes for v6.19We've been quite busy with fixes since the merge window, though not inany particularly exciting ways - the standout thing is the fix for _SXcontrols which were broken by a change to how we do clamping, otherwiseit's all fairly run of the mill fixes and quirks. List of files: /linux/arch/x86/crypto/Makefile

84318277d6334c6981ab326d4acc87c6a6ddc9b8 - Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixes

Mon, 15 Dec 2025 11:53:27 +0000

Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixesPull in rc1 to include all changes since the merge window closed,and grab all fixes and changes from drm/drm-next.Signed-off-by: Maarten Lankhorst List of files: /linux/arch/x86/crypto/Makefile

8f4c9978de91a9a3b37df1e74d6201acfba6cefd - Merge tag 'aes-gcm-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux

Wed, 03 Dec 2025 02:24:35 +0000

Merge tag 'aes-gcm-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linuxPull AES-GCM optimizations from Eric Biggers: "More optimizations and cleanups for the x86_64 AES-GCM code: - Add a VAES+AVX2 optimized implementation of AES-GCM. This is very helpful on CPUs that have VAES but not AVX512, such as AMD Zen 3. - Make the VAES+AVX512 optimized implementation of AES-GCM handle large amounts of associated data efficiently. - Remove the "avx10_256" implementation of AES-GCM. It's superseded by the VAES+AVX2 optimized implementation. - Rename the "avx10_512" implementation to "avx512" Overall, this fills in a gap where AES-GCM wasn't fully optimized on some recent CPUs. It also drops code that won't be as useful as initially expected due to AVX10/256 being dropped from the AVX10 spec"* tag 'aes-gcm-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux: crypto: x86/aes-gcm-vaes-avx2 - initialize full %rax return register crypto: x86/aes-gcm - optimize long AAD processing with AVX512 crypto: x86/aes-gcm - optimize AVX512 precomputation of H^2 from H^1 crypto: x86/aes-gcm - revise some comments in AVX512 code crypto: x86/aes-gcm - reorder AVX512 precompute and aad_update functions crypto: x86/aes-gcm - clean up AVX512 code to assume 512-bit vectors crypto: x86/aes-gcm - rename avx10 and avx10_512 to avx512 crypto: x86/aes-gcm - remove VAES+AVX10/256 optimized code crypto: x86/aes-gcm - add VAES+AVX2 optimized code List of files: /linux/arch/x86/crypto/Makefile

5abe8d8efc022cc78b6273d01e4a453242b9f4d8 - Merge tag 'libcrypto-updates-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux

Wed, 03 Dec 2025 02:01:03 +0000

Merge tag 'libcrypto-updates-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linuxPull crypto library updates from Eric Biggers: "This is the main crypto library pull request for 6.19. It includes: - Add SHA-3 support to lib/crypto/, including support for both the hash functions and the extendable-output functions. Reimplement the existing SHA-3 crypto_shash support on top of the library. This is motivated mainly by the upcoming support for the ML-DSA signature algorithm, which needs the SHAKE128 and SHAKE256 functions. But even on its own it's a useful cleanup. This also fixes the longstanding issue where the architecture-optimized SHA-3 code was disabled by default. - Add BLAKE2b support to lib/crypto/, and reimplement the existing BLAKE2b crypto_shash support on top of the library. This is motivated mainly by btrfs, which supports BLAKE2b checksums. With this change, all btrfs checksum algorithms now have library APIs. btrfs is planned to start just using the library directly. This refactor also improves consistency between the BLAKE2b code and BLAKE2s code. And as usual, it also fixes the issue where the architecture-optimized BLAKE2b code was disabled by default. - Add POLYVAL support to lib/crypto/, replacing the existing POLYVAL support in crypto_shash. Reimplement HCTR2 on top of the library. This simplifies the code and improves HCTR2 performance. As usual, it also makes the architecture-optimized code be enabled by default. The generic implementation of POLYVAL is greatly improved as well. - Clean up the BLAKE2s code - Add FIPS self-tests for SHA-1, SHA-2, and SHA-3"* tag 'libcrypto-updates-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux: (37 commits) fscrypt: Drop obsolete recommendation to enable optimized POLYVAL crypto: polyval - Remove the polyval crypto_shash crypto: hctr2 - Convert to use POLYVAL library lib/crypto: x86/polyval: Migrate optimized code into library lib/crypto: arm64/polyval: Migrate optimized code into library lib/crypto: polyval: Add POLYVAL library crypto: polyval - Rename conflicting functions lib/crypto: x86/blake2s: Use vpternlogd for 3-input XORs lib/crypto: x86/blake2s: Avoid writing back unchanged 'f' value lib/crypto: x86/blake2s: Improve readability lib/crypto: x86/blake2s: Use local labels for data lib/crypto: x86/blake2s: Drop check for nblocks == 0 lib/crypto: x86/blake2s: Fix 32-bit arg treated as 64-bit lib/crypto: arm, arm64: Drop filenames from file comments lib/crypto: arm/blake2s: Fix some comments crypto: s390/sha3 - Remove superseded SHA-3 code crypto: sha3 - Reimplement using library API crypto: jitterentropy - Use default sha3 implementation lib/crypto: s390/sha3: Add optimized one-shot SHA-3 digest functions lib/crypto: sha3: Support arch overrides of one-shot digest functions ... List of files: /linux/arch/x86/crypto/Makefile

7362b5b493102c6b71827c2da22117b475528f6d - Merge branch 'for-6.19/nintendo' into for-linus

Tue, 02 Dec 2025 13:46:11 +0000

Merge branch 'for-6.19/nintendo' into for-linus- switch to WQ_PERCPU workaueues (Marco Crivellari)- reduce potential initialization blocking time of hid-nintendo (Willy Huang) List of files: /linux/arch/x86/crypto/Makefile

2ace52718376fdb56aca863da2eebe70d7e2ddb1 - Merge branch 'objtool/core'

Fri, 21 Nov 2025 10:21:20 +0000

Merge branch 'objtool/core'Bring in the UDB and objtool data annotations to avoid conflicts while further extending the bug exceptions.Signed-off-by: Peter Zijlstra List of files: /linux/arch/x86/crypto/Makefile

f39b6c468c52745dbca9a842d91c8373fda208ab - Merge tag 'v6.18-rc6' into for-linus

Tue, 18 Nov 2025 07:16:55 +0000

Merge tag 'v6.18-rc6' into for-linusSync up with the mainline to bring in definition ofINPUT_PROP_HAPTIC_TOUCHPAD. List of files: /linux/arch/x86/crypto/Makefile

4d8da35579daad0392d238460ed7e9629d49ca35 - lib/crypto: x86/polyval: Migrate optimized code into library

Sun, 09 Nov 2025 23:47:20 +0000

lib/crypto: x86/polyval: Migrate optimized code into libraryMigrate the x86_64 implementation of POLYVAL into lib/crypto/, wiring itup to the POLYVAL library interface. This makes the POLYVAL library beproperly optimized on x86_64.This drops the x86_64 optimizations of polyval in the crypto_shash API.That's fine, since polyval will be removed from crypto_shash entirelysince it is unneeded there. But even if it comes back, the crypto_shashAPI could just be implemented on top of the library API, as usual.Adjust the names and prototypes of the assembly functions to align moreclosely with the rest of the library code.Also replace a movaps instruction with movups to remove the assumptionthat the key struct is 16-byte aligned. Users can still align the keyif they want (and at least in this case, movups is just as fast asmovaps), but it's inconvenient to require it.Reviewed-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20251109234726.638437-6-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/x86/crypto/Makefile

cb9f145f638d7afa633632a9290d6ad06caeb8ee - Merge remote-tracking branch 'drm/drm-next' into msm-next-robclark

Sat, 01 Nov 2025 12:47:30 +0000

Merge remote-tracking branch 'drm/drm-next' into msm-next-robclarkBack-merge drm-next to get caught up.Signed-off-by: Rob Clark List of files: /linux/arch/x86/crypto/Makefile

12beec21c50950cc9a1907750200af4eb99a8aca - crypto: x86/aes-gcm - rename avx10 and avx10_512 to avx512

Thu, 02 Oct 2025 02:31:12 +0000

crypto: x86/aes-gcm - rename avx10 and avx10_512 to avx512With the "avx10_256" code removed and the AVX10 specification havingbeen changed to basically just be a re-packaged AVX512, the "avx10_512"name no longer makes sense. Replace it with "avx512".While doing this, also add the "vaes_" prefix in places that didn'talready have it. The result is that the two VAES optimizedimplementations are consistently called vaes_avx2 and vaes_avx512.(Also drop the "-x86_64" part of the assembly filename, to keep it fromgetting too long. There's no 32-bit version of this code, and the factthat it's 64-bit is unremarkable; it's the norm for new code.)Note: although aes_gcm_aad_update_vaes_avx512() (previously calledaes_gcm_aad_update_vaes_avx10()) uses at most 256-bit vectors, it stilldepends on the AVX512 CPU feature. So its new name is still accurate.Also, a later commit will make it sometimes use 512-bit vectors anyway.Acked-by: Ard Biesheuvel Tested-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20251002023117.37504-4-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/x86/crypto/Makefile

fae3b96ba6015c35a973da09bf313d90e4e4bb94 - crypto: x86/aes-gcm - add VAES+AVX2 optimized code

Thu, 02 Oct 2025 02:31:10 +0000

crypto: x86/aes-gcm - add VAES+AVX2 optimized codeAdd an implementation of AES-GCM that uses 256-bit vectors and thefollowing CPU features: Vector AES (VAES), Vector CarrylessMultiplication (VPCLMULQDQ), and AVX2.It doesn't require AVX512. So unlike the existing VAES+AVX512 code, itworks on CPUs that support VAES but not AVX512, specifically: - AMD Zen 3, both client and server - Intel Alder Lake, Raptor Lake, Meteor Lake, Arrow Lake, and Lunar Lake. (These are client CPUs.) - Intel Sierra Forest. (This is a server CPU.)On these CPUs, this VAES+AVX2 code is much faster than the existingAES-NI code. The AES-NI code uses only 128-bit vectors.These CPUs are widely deployed, making VAES+AVX2 code worthwhile eventhough hopefully future x86_64 CPUs will uniformly support AVX512.This implementation will also serve as the fallback 256-bitimplementation for older Intel CPUs (Ice Lake and Tiger Lake) thatsupport AVX512 but downclock too eagerly when 512-bit vectors are used.Currently, the VAES+AVX10/256 implementation serves that purpose. Alater commit will remove that and just use the VAES+AVX2 one. (Notethat AES-XTS and AES-CTR already successfully use this approach.)I originally wrote this AES-GCM implementation for BoringSSL. It's beenin BoringSSL for a while now, including in Chromium. This is a port ofit to the Linux kernel. The main changes in the Linux version include:- Port from "perlasm" to a standard .S file.- Align all assembly functions with what aesni-intel_glue.c expects, including adding support for lengths not a multiple of 16 bytes.- Rework the en/decryption of the final 1 to 127 bytes.This commit increases AES-256-GCM throughput on AMD Milan (Zen 3) by upto 74%, as shown by the following tables:Table 1: AES-256-GCM encryption throughput change, CPU vs. message length in bytes: | 16384 | 4096 | 4095 | 1420 | 512 | 500 |----------------------+-------+-------+-------+-------+-------+-------+AMD Milan (Zen 3) | 67% | 59% | 61% | 39% | 23% | 27% | | 300 | 200 | 64 | 63 | 16 |----------------------+-------+-------+-------+-------+-------+AMD Milan (Zen 3) | 14% | 12% | 7% | 7% | 0% |Table 2: AES-256-GCM decryption throughput change, CPU vs. message length in bytes: | 16384 | 4096 | 4095 | 1420 | 512 | 500 |----------------------+-------+-------+-------+-------+-------+-------+AMD Milan (Zen 3) | 74% | 65% | 65% | 44% | 23% | 26% | | 300 | 200 | 64 | 63 | 16 |----------------------+-------+-------+-------+-------+-------+AMD Milan (Zen 3) | 12% | 11% | 3% | 2% | -3% |Acked-by: Ard Biesheuvel Tested-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20251002023117.37504-2-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/x86/crypto/Makefile

ec2e0fb07d789976c601bec19ecced7a501c3705 - Merge tag 'asoc-fix-v6.18-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Thu, 16 Oct 2025 18:14:24 +0000

Merge tag 'asoc-fix-v6.18-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Fixes for v6.18A moderately large collection of driver specific fixes, plus a few newquirks and device IDs. The NAU8821 changes are a little large but morein mechanical ways than in ways that are complex. List of files: /linux/arch/x86/crypto/Makefile