Skip to contentSkip to conversation

linux-next: Tree for Sep 29

DISCUSSION Mark Brown 1 participant 1 message Sep 29, 2025 Linux-next tree

lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

Hi all,

There will be no releases on Tueday or Wednesday, they will resume on Thursday.

As a reminder we are in the merge window, please do not add new non-bugfix commits.

Changes since 20250926:

The vfs-brauner tree gained a build failure for which I applied a fixup.

The net-next tree gained a conflict with the v4l-dvb tree.

The vhost tree gained a conflict with the net-next tree.

Non-merge commits (relative to Linus' tree): 11590

 11571 files changed, 552562 insertions(+), 212078 deletions(-)

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

I have created today's linux-next tree at
git://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.