Re: [GIT PULL for v7.4] media updates

[Sasha Levin <sashal@kernel.org>]

On Sat, Oct 31, 2026 at 02:14:37PM -0700, Linus Torvalds wrote:
> It actually broke git this merge window. See
>
>    https://lore.kernel.org/all/20261031065525.19883-2-torvalds@kernel.org/

I was curious which 283 commits describe was overcounting. Funny
enough, they all come from bpf-next-7.3 rather than media, and their
dates seem to make sense.

A bpf series went in with five commits in the same second. A bpf-next-7.4
series without a base-commit then got applied on top of the middle of that run:

  bd2466ed8fc2 ("bpf: Roll back stream capacity when allocation fails")

sits on

  af22d273aa1f ("bpf, arm64: Fix exception table metadata for arena load-acquire")

The media dates seem to come from tooling too: The media CI merges MRs with
Marge-bot, a GitLab merge bot, which rebases each one onto next using
--keep-committers [1]. That copies the original committer date onto every
rebased commit, so an MR landing after a newer one ends up older than its new
parent.

GitLab shows the same pattern for all the commits you found: the copy each
committer pushed sits on an older parent with the same committer date, and the
rebased branch that landed was pushed by marge-bot. For your example, Sakari
pushed the alvium fix on top of

  b38d06ad1e13 ("media: ipu6: Fix up missing IWYU issue")

His MR with

  63c578491cb4 ("media: sun6i-csi: bridge: Use V4L2 subdev active state")

merged at 22:10 UTC on Sep 16, and at 22:11 marge-bot pushed the alvium
MR rebased on top of it, still dated Sep 15.

So in both cases it's the tooling being funny.

[1] https://gitlab.com/marge-org/marge-bot/-/commit/3fb8ab74b8781505530c21a28ac08080bc7deedb

-- 
Thanks,
Sasha