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.4-rc2
Date: Mon, 9 Nov 2026 16:29:59 +0000	[thread overview]
Message-ID: <avH1B9W0Hm3LJSvA@sirena.co.uk> (raw)

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

Hi Linus,

The first week of the cycle has been fairly quiet, only the one build
failure below which will hopefully be addressed soon and a missing
release on Friday due to poor connectivity on the UK train network.  I
think there were more conflicts today resulting from Kees' kmalloc_obj()
treewide stuff than there were in the whole of last week but I didn't
actually count.  The number of commits going in feels relatively low
compared to this point in recent cycles, v7.2-rc2 had 3372, v7.3-rc2 had
3715 but this is only 2367.

Trees being held at old versions:

  leds-lj        	next-20261104

No trees have signoff problems

Non-merge commits relative to Linus' tree: 2367
 2580 files changed, 92721 insertions(+), 30436 deletions(-)

Top trees adding commits to -next:

  359	amdgpu
  195	mm
  189	iio
  169	drm-xe
  168	sound-asoc
  121	drm-intel
  94	mm-nonmm-unstable
  88	vfs-brauner
  70	gpio-brgl
  60	mm-fixes

Trees adding duplicate commits to -next:

 144 amdgpu
  11 drm-intel
   4 watchdog
   2 sysctl
   2 mm-nonmm-unstable
   1 vfs-fixes
   1 fs-next
   1 at91

Thanks,
Mark

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

                 reply	other threads:[~2026-11-09 16:30 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=avH1B9W0Hm3LJSvA@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®