public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Subject: -next status as at v6.19-rc6
Date: Tue, 20 Jan 2026 14:38:05 +0000	[thread overview]
Message-ID: <8aa94614-9fa3-45fb-9e7e-17f147342aff@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-01-20 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8aa94614-9fa3-45fb-9e7e-17f147342aff@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=torvalds@linux-foundation$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox