linux-next: Tree for Aug 7

Hi all,

Changes since 20260806:

The drm tree acquired a conflict with the origin tree.

The drm tree acquired a conflict with the drm-fixes tree.

The drm-rust tree acquired a conflict with the driver-core.current tree.

The amdgpu tree acquired a build failure, I used the tree from
next-20260806 instead.

The kvm tree acquired a conflict with the kvm-fixes tree.

The kvm-arm tree acquired a conflict with the arm64 tree.

The apparmor tree acquired a build failure, I used the tree from
next-20260806 instead.

Non-merge commits (relative to Linus' tree): 12426
 11021 files changed, 579344 insertions(+), 196843 deletions(-)

----------------------------------------------------------------------------

I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There is also the merge.log file in the Next
directory.  Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf.  After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.

Below is a summary of the state of the merge.

I am currently merging 429 trees (counting Linus' and 133 trees of bug
fix patches pending for the current release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Thanks to Paul Gortmaker for triage and bug fixes.

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmp2El8ACgkQJNaLcl1U
h9CYvgf/XZ5o6fr/HYrfRkdeK6KMDxxPr5b9A+IsAZGyvLjzT1+FQgsvFjPFbHTG
8dcksyHGFCg7DpUzDKFA/gJqUW9vFl4usHmrbCsN0ZjBrqaDnId0VNPeqAbblLI/
rXNl1kEBi1sddkrKCCw9FsHxfVrj+ucLaFZDVivhZdKr8CteDfw1SdQwTPbLUlCA
D9oWE7C5HIcFQxOCdqtvyUyD4uZuNV82nRlnYZMT3u7n9zmKtVwcCdP3PFMUteeb
dCw5JUS3PqobkAKLn3tsasDPGLwln91Ff926pgRjCkYYzAN300dOVez/DK0GPAPI
pdZWy/5vy41S4Ii1kLxG7xfUGKzEXw==
=2C9c
-----END PGP SIGNATURE-----