linux-next: Tree for Jul 21
Mark Brown <[email protected]> Tue, 21 Jul 2026 17:54:59 +0100
| Newsgroups | org.kernel.vger.linux-next,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
Hi all, Changes since 20260720: The bpf-next tree acquired a conflict with the net tree. The drm-misc tree acquired a build failure, I have used the version from next-20260720 instead. The battery tree acquired a build failure, I have used the version from next-20260720 instead. The tip tree acquired a conflict with the mm-hotfixes-unstable tree. Non-merge commits (relative to Linus' tree): 7469 7082 files changed, 302697 insertions(+), 111532 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.
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmpfpGIACgkQJNaLcl1U h9APBwf/VhkSOvVHUDF5bfkDY3IizW57z93I+Pe5aShEPpvfObjgZ6ak3WpZe1jB FWKRjLs/SqvqfT8iIppgqMCrjrGu6/HYtqJ2O9Dh62y7qN9tbe70P5/Un/mJRF3f V3oqMdt/OophL5jhj25zp2QiG3Tlo2H2eeHXXGyxhTDu3a0nfODGNliVCznX5wNw k3U57q1l5SnpQ8JHfCQk6BGHzztrFykoLYHiuS4EGabHUr62xsp58yyDu++ScZ5H bme3UR4iZVvldoASl3n2pjWundwLRZm09EYwoN5uYnQyqr+bv1lgZu1pG4L1DH2z NI5cK3qA99kTeE79WRT1w4T4AeWMQQ== =I7pp -----END PGP SIGNATURE-----