Changes in Makefile

41362886881f6af28fdf416be662c02968c37d81 - Merge tag 'loongarch-kvm-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson into HEAD

Tue, 18 Aug 2026 13:11:45 +0200

Merge tag 'loongarch-kvm-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson into HEADLoongArch KVM changes for v7.31. Advertise already-supported capabilities.2. Some bug fixes about timer and MMIO.3. Some hardening about interrupt injection.4. Replace kvm_err() with kvm_pr_unimpl().5. Add FPU/LSX/LASX test cases for selftests. List of files: /linux/lib/test_fortify/Makefile

acbecf60145a2d6259ff3e059fd295cf626ed574 - Merge 7.2-rc7 into usb-next

Fri, 14 Aug 2026 03:17:11 +0200

Merge 7.2-rc7 into usb-nextWe need the USB fixes in here as well to build on top of.Signed-off-by: Greg Kroah-Hartman List of files: /linux/lib/test_fortify/Makefile

c44e278ce02efd0c4be79a8eda1ea6885c1ce5ec - BackMerge tag 'v7.2' into drm-next

Thu, 20 Aug 2026 02:58:44 +0200

BackMerge tag 'v7.2' into drm-nextLinux 7.2There was a lot of conflicts this round between fixes and next,and I'd like to get the merge resolutions that we have in drm-tip.Signed-off-by: Dave Airlie List of files: /linux/lib/test_fortify/Makefile

fab183d632628381b466a41479489541ac0e29a0 - sched_ext: Merge branch 'for-7.3-arena-args' into for-7.3

Mon, 17 Aug 2026 23:20:34 +0200

sched_ext: Merge branch 'for-7.3-arena-args' into for-7.3Pull to receive the __arena argument conversion: 67f1f4a48c24 ("sched_ext: Pass kernel arena pointers to ops_cid callbacks") a8dc810968af ("sched_ext: Convert sub-cap kfuncs to __arena cmask arguments") a05c5b5cb5cf ("sched_ext: Convert scx_bpf_cid_override() to __arena array arguments")along with the bpf-next branch carrying the __arena argument support theydepend on.Conflict in kernel/sched/ext/ext.c between: c384ab8a0b13 ("sched_ext: Move the config-off sub-cap kfunc stubs into sub.c")and: a8dc810968af ("sched_ext: Convert sub-cap kfuncs to __arena cmask arguments")which updated the stubs in their old ext.c location. Resolved by keepingext.c without the stubs and applying the prototype conversion to therelocated stubs in sub.c.Signed-off-by: Tejun Heo List of files: /linux/lib/test_fortify/Makefile

872a8f6b08069d1b4bfb9bf968dc629ab6998908 - Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next into for-7.3-arena-args

Tue, 11 Aug 2026 00:38:03 +0200

Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next into for-7.3-arena-argsPull bpf-next d114bb989367 ("Merge branch'add-arena-argument-support-to-kfuncs-and-struct_ops'") to make the __arenaand __arena__nullable kfunc and struct_ops argument suffixes available. Thesuffixed arguments will be used to convert sched_ext kfuncs and struct_opscallbacks that currently pass arena pointers as scalars and rebase them byhand. List of files: /linux/lib/test_fortify/Makefile

e1d9b82db5447c88405b216f9c5c87daedaa2971 - Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf 7.2-rc7

Fri, 07 Aug 2026 23:04:17 +0200

Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf 7.2-rc7Cross-merge BPF and other fixes after downstream PR.Signed-off-by: Daniel Borkmann List of files: /linux/lib/test_fortify/Makefile

5c458073553f0ef74f5c8db1bd459c87c722a299 - Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

Thu, 23 Jul 2026 23:04:37 +0200

Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/netCross-merge networking fixes after downstream PR (net-7.2-rc6).No conflicts.Adjacent changes:net/ipv4/route.c dbc3791e3b24 ("net: do not send ICMP/NDISC Redirects when peer allocation fails") 7804eaa057fe ("ipv4: snapshot dst.dev in ip_rt_send_redirect() and ip_rt_get_source()")drivers/net/tun.c 23dad2d088df ("tun: no longer rely on RTNL in tun_fill_info()") c3da92af07ea ("Revert "tun/tap: add ptr_ring consume helper with netdev queue wakeup"")drivers/net/ethernet/marvell/octeontx2/af/rvu_npc.c 3bd438a58e91 ("octeontx2-af: Block VFs from clobbering special CGX PKIND state") 5ba5611ef946 ("octeontx2-af: reserve 4 PKINDs for skip-size custom use")drivers/net/wireless/ath/ath12k/core.hdrivers/net/wireless/ath/ath12k/mac.cdrivers/net/wireless/ath/ath12k/peer.c 469d7e6077c1 ("wifi: ath12k: resolve PENDING ML peer ID from MLO_PEER_MAP HTT event") 378e659029d5 ("wifi: ath12k: introduce host_alloc_ml_id hardware parameter") c42b27336eef ("wifi: ath12k: fix survey indexing across bands")Signed-off-by: Jakub Kicinski List of files: /linux/lib/test_fortify/Makefile

146cc263e457ff6055fe7829e4f4f4b0b5d5dd86 - Merge tag 'v7.2' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into gpio/for-next

Tue, 18 Aug 2026 14:21:04 +0200

Merge tag 'v7.2' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into gpio/for-nextLinux 7.2 List of files: /linux/lib/test_fortify/Makefile

dbaafe9cc56a996931eedfe043eb34418cc9cd9b - Merge tag 'v7.2-rc7' into driver-core-next

Mon, 10 Aug 2026 00:36:11 +0200

Merge tag 'v7.2-rc7' into driver-core-nextWe need the driver-core fixes in here as well to build on top of.Signed-off-by: Danilo Krummrich List of files: /linux/lib/test_fortify/Makefile

6ab838a01b12f9d101c26ff8cebbf4029a8c9e09 - regulator: qcom-rpmh: Support RPMH address reads and use it for rpmh-regulators

Fri, 07 Aug 2026 16:19:44 +0200

regulator: qcom-rpmh: Support RPMH address reads and use it for rpmh-regulatorsKamal Wadhwa says:This patch series adds a new `rpmh_read()` API to allow reading RPMHaddresses. Using this API enhances the RPMH regulator driver by addingreadback of the voltage/bypass/mode settings as they have been applied byAPPS during the bootloader stage, so regulator framework can get themvia `get_mode`, `get_bypass` & `get_voltage_selector` callbacks duringregulator registration.This is needed because currently regulator framework does a unnecessarywrite with `min-microvolt` DT setting for all the RPMH regulators duringregulator registration, because the first time after boot the value isseen as -ENOTRECOVERABLE, as there is no option to read these regulatorsettings.With this change this unnecessary write can be avoided and regulatorframework gets a sense of the initial state set during the bootloaderstage for all regulator settings.NOTE - During discussion on the v2 series - PATCH 3/4, reviewer hadinquired about possible need for the use of the sync_state() to handle the"multiple" client case - for maintaining the regulator settings till allthe clients are probed.This case was not covered in my previous series and had originally plannedto do that series separately. But after the discussion decided to mergethe 2 series as it seemed this would be a better approach. But afterworking on sync_state change. I realized a basic issue with usingsync_state() for regulators - that its per-driver and not per-regulatorresource. But we needed a sync_state callback for each regulator separately.I had been experimenting with few ideas but seems its going to need moretime for me to close on the equivalent solution that has per-regulatorsync_state or something to that effect. So I thought to close on thisseries and attend to that separately.Link: https://patch.msgid.link/20260801-b4-read-rpmh-v5-v6-0-9fcb54928523@oss.qualcomm.com List of files: /linux/lib/test_fortify/Makefile

4afd4ac3642a8ff73af331079b0fc0b0ccd0a3df - ASoC: SOF: ipc4-topology: Pipeline params improvements

Tue, 04 Aug 2026 18:31:03 +0200

ASoC: SOF: ipc4-topology: Pipeline params improvementsPeter Ujfalusi says:Improve handling of some corner cases that are not used by current topologydesigns, but can be crafted within the rules of a topology file.For example branching topologies, where a single input routed to multipleoutput endpoints. The already configured part of the graph places constrainton how the new branch can be configured.Handling of process modules also updated to be able to 'guess' whatparameters can be changed by the module and allow flexible operation.Link: https://patch.msgid.link/20260730121729.18673-1-peter.ujfalusi@linux.intel.com List of files: /linux/lib/test_fortify/Makefile

0c8e7a014e5d232d65dfd9488d9ad62b03e6b2aa - spi: Add support for StarFive JHB100 SFC

Tue, 04 Aug 2026 14:47:02 +0200

spi: Add support for StarFive JHB100 SFCChanghuang Liang says:This serial add support for the StarFive JHB100 SoC SPI FlashController (SFC), which is based on the Synopsys DesignWare SSIversion 2.00a but with some customizations and it also addenhanced SPI for DesignWare SPI controllers.I picked up some patches from series [1].This series depends on the series [2]:[1] https://lore.kernel.org/all/20221212180732.79167-1-sudip.mukherjee@sifive.com/[2] https://lore.kernel.org/all/20260521012932.24163-1-changhuang.liang@starfivetech.com/v1: https://lore.kernel.org/all/20260709055204.138168-1-changhuang.liang@starfivetech.com/Link: https://patch.msgid.link/20260803124044.156998-1-changhuang.liang@starfivetech.com List of files: /linux/lib/test_fortify/Makefile

3f8fa8fe90cae74bf7b72c99f30f04e012c5c41b - Merge branch 'sched/urgent'

Fri, 14 Aug 2026 16:12:58 +0200

Merge branch 'sched/urgent'Pull in dependents, the flat hierarchy fix depends on this.Signed-off-by: Peter Zijlstra List of files: /linux/lib/test_fortify/Makefile

9a1fc5ae87312003efc967018278f2c39c2e7f81 - Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixes

Mon, 10 Aug 2026 13:35:50 +0200

Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixesPull in v7.2-rc7.Signed-off-by: Maarten Lankhorst List of files: /linux/lib/test_fortify/Makefile

c6e94cd60b3d199c22242521f0b04de87a02da6e - Merge tag 'v7.2-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into gpio/for-current

Mon, 10 Aug 2026 12:33:47 +0200

Merge tag 'v7.2-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into gpio/for-currentLinux 7.2-rc7 List of files: /linux/lib/test_fortify/Makefile

d03cdb1c3694a0c2334ea7f864660ad8e8672eb9 - Merge tag 'asoc-fix-v7.2-rc6' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Thu, 06 Aug 2026 13:55:51 +0200

Merge tag 'asoc-fix-v7.2-rc6' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Fixes for v7.2A moderately large set of fixes, but mostly unremarkable: - A series of robustness fixes for the SOF code that came from testing. - Fixes for user visible issues with some of the Qualcomm controls. - Fixes to the register default tables in Cirrus drivers which ensure correcy syncing on resume. This is a wider problem which will be fixed with a regmap core change but I'd already applied these, the rest of the fixes will come in the merge window. - Making the existing RT645 driver user selectable so it can be used with more machines. - Quite a few new AMD laptop quirks. - A MAINTAINERS update for SpacemiT. List of files: /linux/lib/test_fortify/Makefile

33c5aaf693d3fb78f6b8a9658939b72b7638243d - ASoC: cs35l41/cs35l45/cs4265: sort the reg_defaults tables

Wed, 05 Aug 2026 14:34:37 +0200

ASoC: cs35l41/cs35l45/cs4265: sort the reg_defaults tablesPeter Ujfalusi says:reg_defaults must be sorted by ascending register address asregcache_lookup_reg() locates the entries in it with bsearch(), see commitfd80df352ba1 ("regcache: Add support for sorting defaults arrays").These three tables have entries which are out of order, so the binary searchdoes not find part of them. For those registers regcache_reg_needs_sync()cannot compare the cached value against the default and reports that a syncis needed, so they are written to the device on every regcache_sync() evenwhen they were never touched.The patches only reorder the existing entries, the text of every entry iskept verbatim and no default value is changed. Each table was verified byevaluating the register addresses and replaying lib/bsearch.c on them.Entries not reachable by the binary search, per table: cs35l41_reg 2 (of 47) cs35l45_defaults 36 (of 73) cs4265_reg_defaults 3 (of 16)For cs35l45 this is nearly half of the table: the DSP1_RX*_RATE andDSP1_TX*_RATE registers sit in the middle of it while their addresses arefar above everything else, which cuts the search off from the whole0x4c40 - 0xf010 range.Found by an audit of all reg_defaults tables under sound/, the SoundWirecodec drivers are fixed by a separate series.Link: https://patch.msgid.link/20260805082413.26174-1-peter.ujfalusi@linux.intel.com List of files: /linux/lib/test_fortify/Makefile

609f036d8b93f17d18dc904eecf50b2b086772f6 - Merge tag 'hardening-v7.2-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux

Tue, 28 Jul 2026 22:36:01 +0200

Merge tag 'hardening-v7.2-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linuxPull hardening fixes from Kees Cook: - lkdtm: fix missed rename of STACKLEAK_ERASING to KSTACK_ERASE (Haofeng Li) - selftests/seccomp: Fix pointer type mismatch build error (Kuan-Ying Lee) - tests/fortify: Disable -Wstringop-overread (Nathan Chancellor)* tag 'hardening-v7.2-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux: selftests/seccomp: Fix pointer type mismatch build error selftests/lkdtm: rename STACKLEAK_ERASING to KSTACK_ERASE fortify: Disable -Wstringop-overread in tests List of files: /linux/lib/test_fortify/Makefile

c1f3e770eec26d6f96dd6d2ea30555ba7c09a244 - fortify: Disable -Wstringop-overread in tests

Tue, 23 Jun 2026 22:23:46 +0200

fortify: Disable -Wstringop-overread in testsclang recently added support for -Wstringop-overread [1], which is on bydefault like -Wfortify-source. This breaks the usage of -Werror in thefortify tests, resulting in the following false positive warnings in thekernel build: warning: unsafe memcmp() usage lacked '__read_overflow2' warning in lib/test_fortify/read_overflow2-memcmp.c warning: unsafe memcmp() usage lacked '__read_overflow' warning in lib/test_fortify/read_overflow-memcmp.c warning: unsafe memchr() usage lacked '__read_overflow' warning in lib/test_fortify/read_overflow-memchr.cExamining the fortify test logs shows a warning like the following ineach of the failed logs: In file included from lib/test_fortify/read_overflow2-memcmp.c:5: lib/test_fortify/test_fortify.h:34:2: error: 'memcmp' reading 17 bytes from a region of size 16 [-Werror,-Wstringop-overread] 34 | TEST; | ^ lib/test_fortify/read_overflow2-memcmp.c:3:2: note: expanded from macro 'TEST' 3 | memcmp(large, small, sizeof(small) + 1) | ^ 1 error generated.Disable -Wstringop-overread for the fortify tests, as it defeats thepurpose of testing the Linux specific implementation of fortify, like-Wfortify-source.Cc: stable@vger.kernel.orgCloses: https://github.com/ClangBuiltLinux/linux/issues/2168Link: https://github.com/llvm/llvm-project/commit/86f2e71cb8d165b59ad31a442b2391e23826133e [1]Signed-off-by: Nathan Chancellor Link: https://patch.msgid.link/20260623-fix-test_fortify-for-clang-stringop-overread-v1-1-15ee8342a953@kernel.orgSigned-off-by: Kees Cook List of files: /linux/lib/test_fortify/Makefile

f088104d837a991c65e51fa30bb4196169b3244d - Merge drm/drm-next into drm-intel-gt-next

Tue, 16 Sep 2025 12:53:20 +0200

Merge drm/drm-next into drm-intel-gt-nextBackmerge in order to get the commit: 048832a3f400 ("drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter")To drm-intel-gt-next as there are followup fixes to be applied.Signed-off-by: Joonas Lahtinen List of files: /linux/lib/test_fortify/Makefile