Changes in Kconfig

962528fef90253aeded29cee20a9b6ff3595fed4 - Merge tag 'gpio-fixes-for-v7.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux

Thu, 25 Jun 2026 18:33:23 +0200

Merge tag 'gpio-fixes-for-v7.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linuxPull gpio fixes from Bartosz Golaszewski: - fix locking context with shared GPIOs in gpio-tegra - fix IRQ domain leak in error path in gpio-davinci - fix returning a potentially uninitialized integer in gpiochip_set_multiple() - use raw spinlock in gpio-eic-sprd and gpio-sch to address locking context issues - bail out of probe() if registering the GPIO chip fails in gpio-mlxbf3 - fix varible type for storing the "ngpios" property in gpio-pisosr - fix out-of-bounds pin access in GPIO ACPI - make GPIO ACPI core only trigger interrupts on boot that are marked as ActiveBoth - fix kerneldoc in gpio-tb10x - reference the real software node of the cs5535 GPIO controller in Geode board file* tag 'gpio-fixes-for-v7.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux: gpio: davinci: fix IRQ domain leak on devm_kzalloc failure gpio: tegra: do not call pinctrl for GPIO direction gpio: tb10x: fix struct tb10x_gpio kernel-doc gpiolib: initialize return value in gpiochip_set_multiple() x86/platform/geode: reference the real node of the cs5535 GPIO controller gpio: eic-sprd: use raw_spinlock_t in the irq startup path gpio: sch: use raw_spinlock_t in the irq startup path gpiolib: acpi: Prevent out-of-bounds pin access in OperationRegion handler gpiolib: acpi: Add robust bounds-checking for GPIO pin resources gpio: mlxbf3: fail probe if gpiochip registration fails gpio: pisosr: Read "ngpios" as u32 gpiolib: acpi: Only trigger ActiveBoth interrupts on boot List of files: /linux/arch/x86/Kconfig

7a0e692a0381254b2f77c54dec100cd3325a6fdf - Merge branch 'next' into for-linus

Tue, 23 Jun 2026 08:10:08 +0200

Merge branch 'next' into for-linusPrepare input updates for 7.2 merge window. List of files: /linux/arch/x86/Kconfig

442d60df742a597dca7cca89a28a4843ce935f09 - x86/platform/geode: reference the real node of the cs5535 GPIO controller

Thu, 11 Jun 2026 09:59:27 +0200

x86/platform/geode: reference the real node of the cs5535 GPIO controllerGPIO software node lookup should rely exclusively on matching theaddresses of the referenced firmware nodes. Commit e5d527be7e69 ("gpio:swnode: don't use the swnode's name as the key for GPIO lookup") tried toenforce this but had to be reverted: it broke existing users who abuse thesoftware node mechanism by creating "dummy" software nodes named after thedevice they want to get GPIOs from, without ever attaching them to theactual GPIO devices. Those users rely on GPIOLIB matching the label of theGPIO controller against the name of the software node rather than on a realfirmware node link.Un-reverting e5d527be7e69 therefore requires converting all such users toreal firmware node lookup. The geode board setup is one of them: itreferences the cs5535 GPIO controller through a locally-defined dummy nodenamed "cs5535-gpio".The cs5535 MFD driver now exports the software node associated with itsGPIO controller cell as cs5535_gpio_swnode. Use it as the target of theGPIO software node references in geode-common.c instead of the dummy node,so the lookup resolves by firmware node address. As the referenced nodemust exist at lookup time, make the cs5535 driver built-in for all boardsselecting GEODE_COMMON (depend on GPIO_CS5535=y). The node is exported inthe "CS5535" namespace, so import it in this module.Acked-by: Borislav Petkov (AMD) Link: https://patch.msgid.link/20260611-cs5535-swnode-v3-1-2b0c517c0c03@oss.qualcomm.comSigned-off-by: Bartosz Golaszewski List of files: /linux/arch/x86/Kconfig

aa776949fb77462ee712eee28bc54a9ce95c5b40 - Merge branch 'for-7.2/wiimote' into for-linus

Tue, 16 Jun 2026 21:47:16 +0200

Merge branch 'for-7.2/wiimote' into for-linus List of files: /linux/arch/x86/Kconfig

ff5ccdb8d5bd242f1064c6f7996603e47e28d095 - Merge tag 'x86-cpu-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip

Mon, 15 Jun 2026 11:55:17 +0200

Merge tag 'x86-cpu-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull x86 cpuid updates from Ingo Molnar: - CPUID API updates (Ahmed S. Darwish): - Introduce a centralized CPUID parser - Introduce a centralized CPUID data model - Introduce - Rename cpuid_leaf()/cpuid_subleaf() APIs - treewide: Explicitly include the x86 CPUID headers - Update to x86-cpuid-db v3.1 (Maciej Wieczor-Retman) - Continued removal of pre-i586 support and related simplifications (Ingo Molnar) - Add Intel CPU model number for rugged Panther Lake (Tony Luck) - Misc fixes, updates and cleanups by Arnd Bergmann, Chao Gao, Lukas Bulwahn, Sohil Mehta, Maciej Wieczor-Retman.* tag 'x86-cpu-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: (25 commits) x86/cpu: Make CONFIG_X86_CX8 unconditional x86/cpu: Remove unused !CONFIG_X86_TSC code x86/cpuid: Update bitfields to x86-cpuid-db v3.1 tools/x86/kcpuid: Update bitfields to x86-cpuid-db v3.1 x86/cpu: Make CONFIG_X86_TSC unconditional MAINTAINERS: Drop obsolete FPU EMULATOR section x86/cpu: Fix a F00F bug warning and clean up surrounding code x86/cpu: Add Intel CPU model number for rugged Panther Lake x86/cpuid: Introduce a centralized CPUID parser x86/cpu: Introduce a centralized CPUID data model x86/cpuid: Introduce x86/cpuid: Rename cpuid_leaf()/cpuid_subleaf() APIs x86/cpu: Do not include the CPUID API header in asm/processor.h Documentation: core-api/cpu_hotplug: Remove stale cpu0_hotplug docs x86/cpu, cpufreq: Remove AMD ELAN support x86/fpu: Remove the math-emu/ FPU emulation library x86/fpu: Remove the 'no387' boot option x86/fpu: Remove MATH_EMULATION and related glue code treewide: Explicitly include the x86 CPUID headers x86/cpu: Remove the CONFIG_X86_INVD_BUG quirk ... List of files: /linux/arch/x86/Kconfig

d8d706a27451c015490d23b4f4764de05e553624 - Merge tag 'objtool-core-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip

Mon, 15 Jun 2026 11:01:58 +0200

Merge tag 'objtool-core-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull objtool updates from Ingo Molnar: - A large series of KLP fixes and improvements, in preparation of the arm64 port (Josh Poimboeuf) - Fix a number of bugs and issues on specific distro, LTO, FineIBT and kCFI configs (Josh Poimboeuf) - Misc other fixes by Josh Poimboeuf and Joe Lawrence* tag 'objtool-core-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: (53 commits) objtool/klp: Cache dont_correlate() result objtool: Improve and simplify prefix symbol detection objtool/klp: Fix kCFI prefix finding/cloning objtool: Grow __cfi_* prefix symbols for all CFI+CALL_PADDING objtool/klp: Fix position-dependent checksums for non-relocated jumps/calls objtool: Add insn_sym() helper objtool/klp: Add correlation debugging output objtool/klp: Rewrite symbol correlation algorithm objtool/klp: Calculate object checksums klp-build: Validate short-circuit prerequisites objtool/klp: Remove "objtool --checksum" klp-build: Use "objtool klp checksum" subcommand objtool/klp: Add "objtool klp checksum" subcommand objtool: Consolidate file decoding into decode_file() objtool/klp: Extricate checksum calculation from validate_branch() objtool: Add is_cold_func() helper objtool: Add is_alias_sym() helper objtool/klp: Handle Clang .data..Lanon anonymous data sections objtool/klp: Create empty checksum sections for function-less object files objtool: Include libsubcmd headers directly from source tree ... List of files: /linux/arch/x86/Kconfig

764e77d868a5b932c709e20ddb5993f9111a841c - Merge tag 'locking-core-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip

Mon, 15 Jun 2026 10:51:14 +0200

Merge tag 'locking-core-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull locking updates from Ingo Molnar: "Futex updates: - Optimize futex hash bucket access patterns (Peter Zijlstra) - Large series to address the robust futex unlock race for real, by Thomas Gleixner: "The robust futex unlock mechanism is racy in respect to the clearing of the robust_list_head::list_op_pending pointer because unlock and clearing the pointer are not atomic. The race window is between the unlock and clearing the pending op pointer. If the task is forced to exit in this window, exit will access a potentially invalid pending op pointer when cleaning up the robust list. That happens if another task manages to unmap the object containing the lock before the cleanup, which results in an UAF. In the worst case this UAF can lead to memory corruption when unrelated content has been mapped to the same address by the time the access happens. User space can't solve this problem without help from the kernel. This series provides the kernel side infrastructure to help it along: 1) Combined unlock, pointer clearing, wake-up for the contended case 2) VDSO based unlock and pointer clearing helpers with a fix-up function in the kernel when user space was interrupted within the critical section. ... with help by André Almeida: - Add a note about robust list race condition (André Almeida) - Add self-tests for robust release operations (André Almeida) Context analysis updates: - Implement context analysis for 'struct rt_mutex'. (Bart Van Assche) - Bump required Clang version to 23 (Marco Elver) Guard infrastructure updates: - Series to remove NULL check from unconditional guards (Dmitry Ilvokhin) Lockdep updates: - Restore self-test migrate_disable() and sched_rt_mutex state on PREEMPT_RT (Karl Mehltretter) Membarriers updates: - Use per-CPU mutexes for targeted commands (Aniket Gattani) - Modernize membarrier_global_expedited with cleanup guards (Aniket Gattani) - Add rseq stress test for CFS throttle interactions (Aniket Gattani) percpu-rwsems updates: - Extract __percpu_up_read() to optimize inlining overhead (Dmitry Ilvokhin) Seqlocks updates: - Allow UBSAN_ALIGNMENT to fail optimizing (Heiko Carstens) Lock tracing: - Add contended_release tracepoint to sleepable locks such as mutexes, percpu-rwsems, rtmutexes, rwsems and semaphores (Dmitry Ilvokhin) MAINTAINERS updates: - MAINTAINERS: Add RUST [SYNC] entry (Boqun Feng) Misc updates and fixes by Randy Dunlap, YE WEI-HONG, Fabricio Parra, Dmitry Ilvokhin and Peter Zijlstra"* tag 'locking-core-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: (36 commits) locking: Add contended_release tracepoint to sleepable locks locking/percpu-rwsem: Extract __percpu_up_read() tracing/lock: Remove unnecessary linux/sched.h include futex: Optimize futex hash bucket access patterns rust: sync: completion: Mark inline complete_all and wait_for_completion MAINTAINERS: Add RUST [SYNC] entry cleanup: Specify nonnull argument index selftests: futex: Add tests for robust release operations Documentation: futex: Add a note about robust list race condition x86/vdso: Implement __vdso_futex_robust_try_unlock() x86/vdso: Prepare for robust futex unlock support futex: Provide infrastructure to plug the non contended robust futex unlock race futex: Add robust futex unlock IP range futex: Add support for unlocking robust futexes futex: Cleanup UAPI defines x86: Select ARCH_MEMORY_ORDER_TSO uaccess: Provide unsafe_atomic_store_release_user() futex: Provide UABI defines for robust list entry modifiers futex: Move futex related mm_struct data into a struct futex: Make futex_mm_init() void ... List of files: /linux/arch/x86/Kconfig

186d3c4e92242351afc24d9784f31cb4cd08a4b7 - Merge tag 'timers-vdso-2026-06-13' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip

Mon, 15 Jun 2026 10:27:13 +0200

Merge tag 'timers-vdso-2026-06-13' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull vdso updates from Thomas Gleixner: - Remove the redundant CONFIG_GENERIC_TIME_VSYSCALL after converting the remaining users over. - Rework and sanitize the MIPS VDSO handling, so it does not handle the time related VDSO if there is no VDSO capable clocksource available. Also stop mapping VDSO data pages unconditionally even if there is no usage possible.* tag 'timers-vdso-2026-06-13' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: MIPS: VDSO: Fold MIPS_CLOCK_VSYSCALL into MIPS_GENERIC_GETTIMEOFDAY MIPS: VDSO: Gate microMIPS restriction on GCC version MIPS: VDSO: Fold MIPS_DISABLE_VDSO into MIPS_GENERIC_GETTIMEOFDAY clocksource/drivers/mips-gic-timer: Only use VDSO_CLOCKMODE_GIC when it is a available MIPS: csrc-r4k: Only use VDSO_CLOCKMODE_R4K when it is a available MIPS: VDSO: Only map the data pages when the vDSO is used MIPS: Introduce Kconfig MIPS_GENERIC_GETTIMEOFDAY vdso/datastore: Always provide symbol declarations MAINTAINERS: Add include/linux/vdso_datastore.h to vDSO block vdso/gettimeofday: Rename __arch_get_vdso_u_timens_data() vdso/treewide: Drop GENERIC_TIME_VSYSCALL vdso/vsyscall: Gate update_vsyscall() behind CONFIG_GENERIC_GETTIMEOFDAY riscv: vdso: Drop CONFIG_GENERIC_TIME_VSYSCALL guard around syscall fallbacks List of files: /linux/arch/x86/Kconfig

73f399414a84d715bb1794182aaea852b11d0962 - Merge tag 'kbuild-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux

Mon, 15 Jun 2026 01:31:15 +0200

Merge tag 'kbuild-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linuxPull Kbuild / Kconfig updates from Nathan Chancellor: "Kbuild: - Remove broken module linking exclusion for BTF - Add documentation around how offset header files work - Include unstripped vDSO libraries in pacman packages - Bump minimum version of LLVM for building the kernel to 17.0.1 and clean up unnecessary workarounds - Use a context manager in run-clang-tools - Add dist macro value if present to release tag for RPM packages - Detect and report truncated buf_printf() output in modpost - Add __llvm_covfun and __llvm_covmap to section whitelist in modpost - Support Clang's distributed ThinLTO mode - Remove architecture specific configurations for AutoFDO and Propeller to ease individual architecture maintenance Kconfig: - Add kconfig-sym-check target to look for dangling Kconfig symbol references and invalid tristate literal values - Harden against potential NULL pointer dereference - Fix typo in Kconfig test comment"* tag 'kbuild-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux: (31 commits) kconfig: tests: fix typo in comment kconfig: Remove the architecture specific config for Propeller kconfig: Remove the architecture specific config for AutoFDO modpost: Add __llvm_covfun and __llvm_covmap to section_white_list kconfig: add kconfig-sym-check static checker kbuild: Remove unnecessary 'T' modifier in cmd_ar_builtin_fixup kbuild: distributed build support for Clang ThinLTO kbuild: move vmlinux.a build rule to scripts/Makefile.vmlinux_a scripts: modpost: detect and report truncated buf_printf() output kbuild: rpm-pkg: append %{?dist} macro to Release tag run-clang-tools: run multiprocessing.Pool as context manager compiler-clang.h: Drop explicit version number from "all" diagnostic macro compiler-clang.h: Remove __cleanup -Wunused-variable workaround kbuild: Remove check for broken scoping with clang < 17 in CC_HAS_ASM_GOTO_OUTPUT x86/entry/vdso32: Remove conditional omission of '.cfi_offset eflags' x86/module: Revert "Deal with GOT based stack cookie load on Clang < 17" x86/build: Drop unnecessary '-ffreestanding' addition to KBUILD_CFLAGS scripts/Makefile.warn: Drop -Wformat handling for clang < 16 riscv: Drop tautological condition from TOOLCHAIN_NEEDS_OLD_ISA_SPEC riscv: Remove tautological condition from selection of ARCH_SUPPORTS_CFI ... List of files: /linux/arch/x86/Kconfig

2bebd986eddb31f9ff1e02e9245a318036280759 - x86/cpu: Make CONFIG_X86_CX8 unconditional

Mon, 27 Apr 2026 08:11:18 +0200

x86/cpu: Make CONFIG_X86_CX8 unconditionalI.e. from now on it's a boot time requirement for the CPU to support it.( This was preceded by the removal of all non-CX8 platform build options, so it should have no functional effects in theory. )Signed-off-by: Ingo Molnar Reviewed-by: Arnd Bergmann Acked-by: Dave Hansen Cc: Ahmed S . Darwish Cc: Andrew Cooper Cc: Ard Biesheuvel Cc: H . Peter Anvin Cc: John Ogness Cc: Linus Torvalds Cc: Peter Zijlstra Link: https://lore.kernel.org/r/20250425084216.3913608-14-mingo@kernel.org List of files: /linux/arch/x86/Kconfig

2566fa7b2f2402a77dae6a5e9b28a1bae1c20793 - kconfig: Remove the architecture specific config for Propeller

Thu, 04 Jun 2026 21:56:08 +0200

kconfig: Remove the architecture specific config for PropellerThe CONFIG_PROPELLER_CLANG option currently depends onARCH_SUPPORTS_PROPELLER_CLANG, but this dependency seems unnecessary.Remove ARCH_SUPPORTS_PROPELLER_CLANG and allow users to controlPropeller builds solely through CONFIG_PROPELLER_CLANG. This simplifiesthe kconfig and avoids potential confusion.Move the .llvm_bb_addr_map sections grouping toinclude/asm-generic/vmlinux.lds.h.The Propeller documentation has been updated to reflect the mostrecent tool location and now includes instructions for arm64.Contributor Acknowledgments: * SPE instructions: Daniel Hoekwater Signed-off-by: Rong Xu Suggested-by: Will Deacon Suggested-by: Nathan Chancellor Tested-by: Yabin Cui Reviewed-by: Kees Cook Link: https://patch.msgid.link/20260604195612.3757860-3-xur@google.comSigned-off-by: Nathan Chancellor List of files: /linux/arch/x86/Kconfig

e88b2fe8b9993c9cae856019b1c31c14b63cad7a - kconfig: Remove the architecture specific config for AutoFDO

Thu, 04 Jun 2026 21:56:07 +0200

kconfig: Remove the architecture specific config for AutoFDOThe CONFIG_AUTOFDO_CLANG option currently depends onARCH_SUPPORTS_AUTOFDO_CLANG, but this dependency seems unnecessary.Remove ARCH_SUPPORTS_AUTOFDO_CLANG and allow users to control AutoFDObuilds solely through CONFIG_AUTOFDO_CLANG. This simplifies the kconfigand avoids potential confusion.Expand the AutoFDO documentation to include instructions for arm64.Contributor acknowledgments: * SPE instructions: Daniel Hoekwater * ETM instructions: Yabin Cui Signed-off-by: Rong Xu Suggested-by: Will Deacon Tested-by: Yabin Cui Reviewed-by: Kees Cook Link: https://patch.msgid.link/20260604195612.3757860-2-xur@google.comSigned-off-by: Nathan Chancellor List of files: /linux/arch/x86/Kconfig

a2274cc0091ed4fdce10fad68d08c529b8d3e7dd - x86/vdso: Implement __vdso_futex_robust_try_unlock()

Tue, 02 Jun 2026 11:10:12 +0200

x86/vdso: Implement __vdso_futex_robust_try_unlock()When the FUTEX_ROBUST_UNLOCK mechanism is used for unlocking (PI-)futexes,then the unlock sequence in userspace looks like this: 1) robust_list_set_op_pending(mutex); 2) robust_list_remove(mutex); lval = gettid(); 3) if (atomic_try_cmpxchg(&mutex->lock, lval, 0)) 4) robust_list_clear_op_pending(); else 5) sys_futex(OP,...FUTEX_ROBUST_UNLOCK);That still leaves a minimal race window between #3 and #4 where the mutexcould be acquired by some other task which observes that it is the lastuser and: 1) unmaps the mutex memory 2) maps a different file, which ends up covering the same addressWhen then the original task exits before reaching #5 then the kernel robustlist handling observes the pending op entry and tries to fix up user space.In case that the newly mapped data contains the TID of the exiting threadat the address of the mutex/futex the kernel will set the owner died bit inthat memory and therefore corrupt unrelated data.Provide a VDSO function which exposes the critical section window in theVDSO symbol table. The resulting addresses are updated in the task's mmwhen the VDSO is (re)map()'ed.The core code detects when a task was interrupted within the criticalsection and is about to deliver a signal. It then invokes an architecturespecific function which determines whether the pending op pointer has to becleared or not. The unlock assembly sequence on 64-bit is: mov %esi,%eax // Load TID into EAX xor %ecx,%ecx // Set ECX to 0 lock cmpxchg %ecx,(%rdi) // Try the TID -> 0 transition .Lstart: jnz .Lend movq %rcx,(%rdx) // Clear list_op_pending .Lend: retSo the decision can be simply based on the ZF state in regs->flags. Thepending op pointer is always in DX independent of the build mode(32/64-bit) to make the pending op pointer retrieval uniform. The size ofthe pointer is stored in the matching criticial section range struct andthe core code retrieves it from there. So the pointer retrieval functiondoes not have to care. It is bit-size independent: return regs->flags & X86_EFLAGS_ZF ? regs->dx : NULL;There are two entry points to handle the different robust list pending oppointer size: __vdso_futex_robust_list64_try_unlock() __vdso_futex_robust_list32_try_unlock()The 32-bit VDSO provides only __vdso_futex_robust_list32_try_unlock().The 64-bit VDSO provides always __vdso_futex_robust_list64_try_unlock() andwhen COMPAT is enabled also the list32 variant, which is required tosupport multi-size robust list pointers used by gaming emulators.The unlock function is inspired by an idea from Mathieu Desnoyers.Signed-off-by: Thomas Gleixner Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: André Almeida Acked-by: Uros Bizjak Link: https://lore.kernel.org/20260311185409.1988269-1-mathieu.desnoyers@efficios.comLink: https://patch.msgid.link/20260602090535.883796247@kernel.org List of files: /linux/arch/x86/Kconfig

7b125c44d0b7f617ee81dffd14ce116149d03cb6 - x86: Select ARCH_MEMORY_ORDER_TSO

Tue, 02 Jun 2026 11:09:47 +0200

x86: Select ARCH_MEMORY_ORDER_TSOThe generic unsafe_atomic_store_release_user() implementation does: if (!IS_ENABLED(CONFIG_ARCH_MEMORY_ORDER_TSO)) smp_mb(); unsafe_put_user();As x86 implements Total Store Order (TSO) which means stores imply release,select ARCH_MEMORY_ORDER_TSO to avoid the unnecessary smp_mb().Signed-off-by: Thomas Gleixner Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: André Almeida Link: https://patch.msgid.link/20260602090535.564499644@kernel.org List of files: /linux/arch/x86/Kconfig

96942092d5e67c71af246fa3bc1422cdf80a5dc9 - vdso/treewide: Drop GENERIC_TIME_VSYSCALL

Tue, 19 May 2026 08:26:17 +0200

vdso/treewide: Drop GENERIC_TIME_VSYSCALLThis Kconfig symbol is not used anymore, remove it.Signed-off-by: Thomas Weißschuh Signed-off-by: Thomas Gleixner Link: https://patch.msgid.link/20260519-vdso-generic_time_vsyscal-v1-3-5c2a5905d5f5@linutronix.de List of files: /linux/arch/x86/Kconfig

fff88709f9a9153af85b5224b4594caa5387ca60 - Merge tag 'v7.1-rc6' into next

Mon, 01 Jun 2026 04:43:25 +0200

Merge tag 'v7.1-rc6' into nextSync up with mainline to pull in a fix to IMS PCU driver and otherenhancements. List of files: /linux/arch/x86/Kconfig

111cbb4596e336373ab93e202918f4cdbf78a4c3 - x86/cpu: Make CONFIG_X86_TSC unconditional

Fri, 25 Apr 2025 10:42:08 +0200

x86/cpu: Make CONFIG_X86_TSC unconditionalI.e. it's a boot time requirement for the CPU to support it.This only removes the Kconfig glue, removal of all nowdead !X86_TSC code will happen in a separate patch.Signed-off-by: Ingo Molnar Reviewed-by: Arnd Bergmann Acked-by: Dave Hansen Cc: Linus Torvalds Link: https://lore.kernel.org/r/20250425084216.3913608-12-mingo@kernel.org List of files: /linux/arch/x86/Kconfig

639609b83f69fe4cd08e01423ae8e12d84484cfa - Merge branch 'arena_direct_access' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next into for-7.2

Mon, 25 May 2026 21:34:24 +0200

Merge branch 'arena_direct_access' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next into for-7.2 List of files: /linux/arch/x86/Kconfig

5c8cbca290acdd49a694b36c0af76ba0c00bbf12 - Merge branch '20260507-ubwc-rework-v4-4-c19593d20c1d@oss.qualcomm.com' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into HEAD

Thu, 21 May 2026 22:36:50 +0200

Merge branch '20260507-ubwc-rework-v4-4-c19593d20c1d@oss.qualcomm.com' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into HEADMerge the branch with the soc/qcom changes, required for the next UBWCpatches.Signed-off-by: Dmitry Baryshkov List of files: /linux/arch/x86/Kconfig

09d6818d3bdc1ea6e49a425040528cbdbc97bc0a - Merge branch 'linus' into timers/clocksource

Mon, 18 May 2026 11:01:07 +0200

Merge branch 'linus' into timers/clocksource... to bring it up to date for new changes. List of files: /linux/arch/x86/Kconfig