linux-next: Tree for Sep 15
Mark Brown
maintainerHi all,
Changes since 20250912:
The vfs tree gained multiple conflicts with the vfs-next tree
The rockchip tree gained a conflict with the arm-soc tree.
The fs-next tree gained a conflict with the mm-unstable tree.
The vfs tree gained a build failure for which I applied a patch.
The i2c tree gained a conflict with the arm-soc tree.
The i3c tree gained a build failure, I used the version from 20250912.
The drm-xe tree gained a conflict with Linus' tree.
The tip tree gained a conflict with the block tree.
The bitmap tree gained a conflict with the tip tree.
Non-merge commits (relative to Linus' tree): 8490
9067 files changed, 394959 insertions(+), 164777 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree atgit://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://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 an arm64 defconfig, an allmodconfig for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf.
Below is a summary of the state of the merge.
I am currently merging 407 trees (counting Linus' and 406 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 Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes.