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, 21 Sep 2026 16:21:02 +0200	[thread overview]
Message-ID: <arE9Ts2QCtLLuOXj@sirena.co.uk> (raw)

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

Hi Linus,

Things continue to tick along in a farily normal pattern for this point
in the cycle, quite a few conflicts but nothing too remarkable other
than continuing issue stemming from the messed up merge between amdgpu
and drm-misc which none of the DRM people seem worried about - I expect
that will be resolved in the drm tree before you see it.

Trees being held at old versions:

  amdgpu         	next-20260917	(clang symbol length issue, not
                                         related to the merge issue)

Trees with signoff problems:

  vfs-brauner-fixes	(missing author, new today)

Non-merge commits relative to Linus' tree: 7602
 8221 files changed, 431806 insertions(+), 139589 deletions(-)

Top trees adding commits to -next:

  1064	drm
  526	mm
  471	net-next
  256	v4l-dvb
  225	sound-asoc
  200	qcom
  180	drm-misc
  178	bpf-next
  165	tip
  147	iio

Trees adding duplicate commits to -next:

  16 drm
  12 drm-xe
  10 amdgpu
   9 clockevents
   4 i2c-rust
   4 i2c-andi-fixes
   3 drm-intel
   2 socfpga
   2 pinctrl
   2 configfs

Thanks,
Mark

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

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 14:21 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-14 16:25 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=arE9Ts2QCtLLuOXj@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®