linux-kernel - -next status as at v6.19-rc6

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: <8aa94614-9fa3-45fb-9e7e-17f147342aff@sirena.org.uk>
Date: Tue, 20 Jan 2026 14:38:05 +0000
From: Mark Brown <broonie@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: -next status as at v6.19-rc6

Hi Linus,

You asked for status summaries for -next as we get towards the end of
the release cycles so I figured this was a good time to start trying
that.  Not sure if this is useful to you, or what other information
might be helpful.

Trees currently held at old versions due to build breaks:

driver-core	next-20260116
iio		next-20260116
iommu		next-20260116
leds-lj		next-20260108
perf		next-20260116

We also have the Tyr driver marked as BROKEN in the drm-rust tree
because it does not compile (Rust got picked up by all*config since I
installed the toolchain in preparation for running rust specific checks).

There are currently signoff problems in these trees:

at24
drivers-x86-fixes
risc-v-fixes
spacemit

I was also thinking about trying to do something about pulling testing
status from KernelCI and flagging regressions that they are seeing but I
didn't actually do anything about that yet.

Thanks,
Mark

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