linux-next: Tree for Aug 17

Hi all,

Changes since 20260814:

The net-next tree acquired a conflict with the origin tree.

The clk tree acquired a build failure, I used the tree from
next-20260814 instead.

The drm tree acquired a conflict with the origin tree.

The drm tree lost it's build failure.

The fbdev tree lost it's build failure.

The driver-core tree acquired a conflict with the pm tree.

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

The kunit tree acquired a conflict with the spi tree.

Non-merge commits (relative to Linus' tree): 14621
 12628 files changed, 859191 insertions(+), 259750 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/qJNaLcl1Uh9AFAmqDQJQACgkQJNaLcl1U
h9DUhQf9Fvo5w/bmbFjHCcx76fn9zJPzHlED6QL3D++jqjDfOsrf3UwXknVsdyJ3
KrfY947Nemydfeiv5RQCJ1KQZlJa1K6h0Q1ay1sdIoFdwVN8L29jStFODfxnCv2a
imcIuR8Qbj782AxCtZhSauS9IGfOps3cIzwBony1smwYCjuUPKW1PMP8lFvB+kjV
WMwfM0kFrKb36UXqfQDifyidUYVzv+5NxF+bB98F1JD8kmVvBGHpuUF56bZvjBlT
LS+2jJgD0M96j/2+A7Gx+THr52vcIhKhWBYCgu0+sGhRQSULlVsuPE0HrDJDNBYm
diEPhW6gkH6brunqyx+smJeQHyn4Nw==
=JNCq
-----END PGP SIGNATURE-----