linux-next: Tree for Aug 10

Hi all,

Changes since 20260807:

The pm tree acquired a build failure, I used the version from
next-20260807 instead.

The thermal tree acquired a build failure, I used the version from
next-20260807 instead.

The drm tree acquired multiple conflicts with the origin tree.

The drm tree acquired a build failure, I used the version from
next-20260807 instead.

The apparmor tree lost it's build failure.

The tip tree acquired a conflict with the rust tree.

The char-misc tree acquired a conflict with the tip tree.

Non-merge commits (relative to Linus' tree): 12849
 11385 files changed, 622107 insertions(+), 203793 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/qJNaLcl1Uh9AFAmp6C14ACgkQJNaLcl1U
h9DpAgf7BQMV5ueiOCSob0FDqleTNUSulKQxgfF0kXvRRwFFNJJFdebAdpnlQP1j
glLIkPCxMC+r/Xis2pz2WCq6JGLeIfl8P+WVuVkQWYqp+XotUzwax2lqgy1Dll9l
+rKpNJsVdFPCJdSPPQIAVlm05W2YqGbFCWNghFQ9gPKKYY29xnNB+Vy6KTi+MlUn
Tf/dJDxJo6CTdGVrUg5WD0pNqq3Kw4NZRw1cta9G/7SuQPw+sY+Hho7il2tZcsha
ANV8C1Fl6LJDvZcUyXqQMf5z4EVeTjOc6hT1QVfICiXHML7OccgI1lOdpHDF8gLw
YE6ILLYm2YTxO16XUaEDF/7dF6RcIg==
=Dn3l
-----END PGP SIGNATURE-----