mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: -next status as at v7.3
Date: Mon, 19 Oct 2026 20:09:12 +0100	[thread overview]
Message-ID: <atZq2EZCQ-65sPv1@sirena.co.uk> (raw)

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

Hi Linus,

The usual rush of last minute merge conflicts today so this is a bit
late and rushed but generally everything has been fairly standard - we
did get more issues this week than usual, I guess LPC did slow things
down noticably so it probably evens out.

Trees being held at old versions:

  landlock       	next-20261001	(kunit test failure)

Trees with signoff problems:

  clk		(missing committer)
  drivers-x86	(missing author)
  fs-next	(missing author)
  fuse		(missing author)

Non-merge commits relative to Linus' tree: 16246
 15182 files changed, 1033397 insertions(+), 388934 deletions(-)

Top trees adding commits to -next:

  2236	drm
  1831	net-next
  1243	arm-soc
  781	mm
  619	bpf-next
  596	v4l-dvb
  453	sound-asoc
  378	perf
  342	char-misc
  275	tip

Trees adding duplicate commits to -next:
  23 net-next
  23 drm-misc
  21 drm
  20 drm-xe
  13 nvmem
  13 drm
  12 amdgpu
   9 clockevents
   6 slimbus
   6 phy-next
   4 i2c-rust
   4 fastrpc
   2 vfs-brauner
   2 tip
   2 sysctl
   2 socfpga
   2 devicetree
   2 arm-soc

Thanks,
Mark

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

                 reply	other threads:[~2026-10-20  9:45 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=atZq2EZCQ-65sPv1@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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

all inboxes | Powered by JetHome®