Linux-Next discussions
 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.2-rc7
Date: Mon, 10 Aug 2026 23:43:01 +0100	[thread overview]
Message-ID: <cd671cfe-eec0-4101-898f-9fd4796de7f9@sirena.org.uk> (raw)

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

Hi Linus,

Everything seems to be roughly on track for this point in the release
cycle, nothing jumps out as unusual.  We've lost all the allyesconfig
issues there had been for a couple of weeks.

Trees being held at old versions:

  amdgpu         	next-20260806  (long symbol name from KASAN)
  drm           	next-20260807  (amdgpu issue got sent upstream)
  pm             	next-20260807  (missing file, same issue as thermal)
  thermal        	next-20260807

Trees with signoff problems:

  arm-soc		(missing author)
  arm-soc		(missing committer)
  driver-core		(missing committer)
  gpio-brgl-fixes	(missing committer)

The driver-core and arm-soc ones are rebase issues.

Non-merge commits relative to Linus' tree: 12849
 11385 files changed, 622107 insertions(+), 203793 deletions(-)

Top trees adding commits to -next:

  1739	drm
  1134	net-next
  829	arm-soc
  531	sound-asoc
  500	mm-stable
  339	tip
  306	v4l-dvb
  262	bpf-next
  261	vfs-brauner
  232	iio

Trees adding more than one duplicate commits to -next:

 111 drm
  17 nfc
   8 hyperv-fixes
   4 drm-intel
   3 vfs-brauner
   3 iommu
   2 pinctrl
   2 mediatek
   2 drm-xe
   2 char-misc

Thanks,
Mark

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

                 reply	other threads:[~2026-08-10 22:43 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=cd671cfe-eec0-4101-898f-9fd4796de7f9@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