Message-ID: <aW6wnF0E3BPovw3m@sirena.org.uk>
Date: Mon, 19 Jan 2026 22:30:52 +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>,
	Shuah Khan <shuah@...nel.org>,
	Shuah Khan <skhan@...uxfoundation.org>,
	linux-kselftest@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>,
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
	Björn Roy Baron <bjorn3_gh@...tonmail.com>,
	Benno Lossin <lossin@...nel.org>,
	Andreas Hindborg <a.hindborg@...nel.org>,
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
	Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org
Subject: linux-next: Tree for Jan 19

Hi all,

Changes since 20260116:

I have started verifying the build of a substantial subset of the
kselftests on arm64, some of the skipped builds are simply missing build
dependencies on my machine rather than actual failures - I'll poke at
this over time.  The subset is listed in Next/kselftest-targets.

It also appears that due to having a Rust toolchain on the build server
allmodconfig and allyesconfig have picked up CONFIG_RUST=y coverage.

The vfs tree gained a conflict with the vfs-brauner tree.

The vfs-brauner tree gained a build conflcit with the ntfs3 tree for
which I applied a fixup.

The rust-pin-init tree gained a conflict with the rust-fixes tree.

The xilinx tree gained a conflict with the ti tree.

The perf tree gained a build failure, I have used the version from
20260116 instead.

The drm tree gained multiple conflicts with Linus' tree.

The drm-misc tree gained a build conflict with the drm tree for which I
applied a fixup.

The block tree gained a build failure for which I did a revert.

The iommu tree gained a build failure, I used the version from 20260116.

The iio tree gained a build failure, I used the version from 20260116.

The drm-rust tree gained multiple build failures for which I disabled
the Tyr driver.

Non-merge commits (relative to Linus' tree): 7291
 7092 files changed, 419068 insertions(+), 146354 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 405 trees (counting Linus' and 122 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)

Powered by blists - more mailing lists