linux-kernel - linux-next: Tree for Jan 26

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <aXf_QXYQW59bMKbG@sirena.org.uk>
Date: Mon, 26 Jan 2026 23:56:49 +0000
From: Mark Brown <broonie@...nel.org>
To: Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linux-next: Tree for Jan 26

Hi all,

Changes since 20260123:

The gfs2 tree gained a conflict with Linus' tree.

The ntfs3 tree gained a build failure due to an interaction with Linus'
tree for which I applied a fixup.

The arm64 tree gained a conflict with Linus' tree.

The mm-unstable tree gained a conflict with the fs-next tree.

The jc_docs tree gained a conflcit with the mm-nomm-stable tree.

The jc_docs tree gained a conflcit with the kbuild tree.

The jc_docs tree gained a conflict with Linus' tree.

The thermal tree gained a conflict with the pm tree.

The net-next tree gained a build failure, I used the version from
20260123.

The drm-next tree gained a conflict with the mm-unstable tree.

The block lost it's build failure.

The mailbox tree gained a conflict with the qcom tree.

The kvm-x86 tree gained a conflict with the kvm-arm tree.

The driver-core gained a conflict with the jc_docs tree.

The scsi tree gained a conflict with the libata tree.

The kselftest tree gained a conflict with the block tree.

The cxl tree gained a conflict with the tip tree.

One of the mm trees gained a build failure for which I reverted a
commit.

Non-merge commits (relative to Linus' tree): 8791
 8687 files changed, 509076 insertions(+), 178448 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 a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests 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. And finally, a
simple boot test of the powerpc pseries_le_defconfig kernel in qemu
(with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 404 trees (counting Linus' and 121 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.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)