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-rc4
Date: Mon, 14 Sep 2026 17:25:31 +0100	[thread overview]
Message-ID: <aqgf-6P5reFfRbAt@sirena.co.uk> (raw)

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

Hi Linus,

Things are starting to get busy again, but not in a particulary unusual
fashion other than a big amdgpu conflict that I totally messed up, you
should ignore my resolutions around that in the unlikely event that the
drm people don't sort it before sending stuff to you.

Trees being held at old versions:

  phy-next       	next-20260911

Trees with signoff problems:

  arm-soc	(missing author)
  arm-soc	(missing committer)
  block		(missing committer, new and should be sorted today)
  bluetooth	(missing committer)

Some of the Bluetooth issues got sorted but they introduced further
issues afterwards, I *think* this all ends up getting sorted out with
whatever rebasing thing they do.

Non-merge commits relative to Linus' tree: 5814
 6145 files changed, 320550 insertions(+), 91662 deletions(-)

Top trees adding commits to -next:

  652	amdgpu
  412	drm
  407	mm
  314	net-next
  212	v4l-dvb
  165	qcom
  149	sound-asoc
  143	vfs-brauner
  138	bpf-next
  113	bluetooth

Trees adding duplicate commits to -next:

  46 bluetooth
  31 amdgpu
   9 clockevents
   4 i2c-rust
   4 drm
   3 mm-nonmm-unstable
   3 drm-xe
   2 configfs

Thanks,
Mark

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

             reply	other threads:[~2026-09-14 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 16:25 Mark Brown [this message]
2026-09-14 16:26 ` -next status as at v7.3-rc3 Mark Brown

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=aqgf-6P5reFfRbAt@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®