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-rc4
Date: Mon, 16 Nov 2026 22:01:32 +0000	[thread overview]
Message-ID: <fdb4a794-36cd-457a-93f4-7196d2d03e33@sirena.org.uk> (raw)

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

Hi Linus,

Other than the issues with the kmalloc_obj() treewide change things seem
to be fairly standard at the minute, the number of other conflicts and
build failures seem relatively low.  Commit volume is back to normal
however, last week was a scripting failure rather than a reflection of
reality.

Trees being held at old versions:

  battery        	next-20261113

Trees with signoff problems:

  asm-generic	(missing committer)
  thermal	(missing committer)

Non-merge commits relative to Linus' tree: 6550
 6825 files changed, 328142 insertions(+), 125221 deletions(-)

Top trees adding commits to -next:

  885	drm
  314	qcom
  305	bpf-next
  297	mm
  248	net-next
  212	hwmon-staging
  189	iio
  165	mm-nonmm-unstable
  157	vfs-brauner
  154	drm-intel

Trees adding duplicate commits to -next:
  102 amdgpu
   50 drm
   20 vfs-brauner
   20 drm-intel
   13 btrfs
   12 btrfs-fixes
    3 perf
    3 drm
    2 sysctl
    2 mm-nonmm-unstable
    2 leds-lj
    2 drm-intel


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

                 reply	other threads:[~2026-11-16 22:01 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=fdb4a794-36cd-457a-93f4-7196d2d03e33@sirena.org.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®