-next status as at v7.4-rc1

[Mark Brown]

Hi Linus,

The second half of the merge window ran pretty smoothly, and there's not
been enough time for people to do too much fun so everything is quiet at
the minute.  

I do see quite a lot of commits that didn't make it into mainline over
the merge window, most of that appears to just be trees that rebase
routinely so the actual code will have been merged but I do see a lot of
DRM commits where that shouldn't be the case - copying David in case
there's something more than just people not adjusting what gets pushed
into -next going on there.

No trees are held at old versions but I dropped the turbostat tree today
as there seems to be some rebase confusion which resulted in it having
something that diverged prior to whatever was sent to mainline over the
weekend with horrible conflicts.

Trees with signoff problems:

  mm-fixes	(missing author)
  mm		(missing author)

(the same commit in both)

Non-merge commits relative to Linus' tree: 1906
 1782 files changed, 77157 insertions(+), 27681 deletions(-)

Top trees adding commits to -next:

  238	amdgpu
  151	mm-fixes
  146	drm-xe
  85	drm-intel
  81	mm-nonmm-unstable
  57	btrfs
  53	nfsd
  50	sound-asoc
  49	bpf-next
  47	rockchip

Trees adding duplicate commits to -next:
  60 amdgpu
  23 turbostat
  13 nvmem
  10 drm-intel
   8 drm-xe
   6 slimbus
   4 fastrpc
   3 socfpga
   3 drm-intel
   2 sysctl
   2 riscv-soc-fixes
   1 vfs-fixes
   1 at91

Top trees with commits in next-20261019 that didn't get merged:

  210	mm
  96	amdgpu
  91	ntfs
  84	drm-xe
  82	ksmbd
  81	drivers-x86
  69	ieee1394
  32	paulmck
  32	btrfs
  31	mm-nonmm-unstable

Thanks,
Mark

Attachment: signature.asc
Description: PGP signature