Merge v6.13 into drm-next
A regression was caused by commit e4b5ccd3 ("drm/v3d: Ensure job pointer is set to NULL after job completion"), but this commit is not yet in next-fixes, fast-forward it. Note that this recreates Linus merge in 96c84703 ("Merge tag 'drm-next-2025-01-17' of https://gitlab.freedesktop.org/drm/kernel" ) because I didn't want to backmerge a random point in the merge window. Signed-off-by:Simona Vetter <simona.vetter@ffwll.ch>
Loading
Please sign in to comment