Skip to contentSkip to conversation

-next status as at v7.3-rc4

DISCUSSION Mark Brown 1 participant 2 messages Sep 14 Linux-next tree

lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

Hi Linus,

Things are starting to get busy again, but not in a particulary unusual fashion other than a big amdgpu conflict that I totally messed up, you should ignore my resolutions around that in the unlikely event that the drm people don't sort it before sending stuff to you.

Trees being held at old versions:

phy-next next-20260911

Trees with signoff problems:

arm-soc (missing author)
arm-soc (missing committer)
block (missing committer, new and should be sorted today)
bluetooth (missing committer)

Some of the Bluetooth issues got sorted but they introduced further issues afterwards, I *think* this all ends up getting sorted out with whatever rebasing thing they do.

Non-merge commits relative to Linus' tree: 5814

 6145 files changed, 320550 insertions(+), 91662 deletions(-)

Top trees adding commits to -next:

652 amdgpu
412 drm
407 mm
314 net-next
212 v4l-dvb
165 qcom
149 sound-asoc
143 vfs-brauner
138 bpf-next
113 bluetooth

Trees adding duplicate commits to -next:

46 bluetooth
31 amdgpu
9 clockevents
4 i2c-rust
4 drm
3 mm-nonmm-unstable
3 drm-xe
2 configfs

Thanks,
Mark

author maintainer
#1 lore raw

Re: -next status as at v7.3-rc3

Quoted 6 lines · Mark Brown

Hi Linus,

Things are starting to get busy again, but not in a particulary unusual fashion other than a big amdgpu conflict that I totally messed up, you should ignore my resolutions around that in the unlikely event that the drm people don't sort it before sending stuff to you.

Great though my ability to see the future may be my ability to typo things is greater.