08:20 biju: mripard: Just a question when will the drm-misc-next point to linux-next? Currently only patches in drm-misc-next-fixes appears in next
08:30 mripard: biju: when rc1 is released
08:32 biju: mripard: Thanks
08:45 tzimmermann: PSA: With the merge window comming to an end, drm-misc-next-fixes is now closed again. After -rc1 has been released, relevant fixes go into drm-misc-fixes. Patches in -fixes branches should be small and have a Fixes tag. New features always go into drm-misc-next.
12:10 CounterPillow: lumag: if you have the time, a quick "this is fine" vs "please no" on color format v13 would be appreciated so I can roll up any requested changes into v14. Specifically want to know if my bridge connector based thing for "is this hdmi? if so, use hdmi format" is finally satisfactory:
12:10 CounterPillow: https://lore.kernel.org/dri-devel/20260413-color-format-v13-4-ab37d4dfba48@collabora.com/
12:10 CounterPillow: https://lore.kernel.org/dri-devel/20260413-color-format-v13-5-ab37d4dfba48@collabora.com/
12:10 CounterPillow: https://lore.kernel.org/dri-devel/20260413-color-format-v13-6-ab37d4dfba48@collabora.com/
12:32 tomba: tzimmermann: We've got a fix in drm-misc-next, 3e9a1da270ddff449b1ad9eadc958f43bc204bd2. But that one is a fix to a commit that has already gone to linus' tree. Can I cherry pick and push that fix to drm-misc-fixes, even if that results in a duplicate commit?
12:35 tzimmermann: tomba, of course. the fix also looks important. 'dim cherry-pick' will automatically mention the original git hash in the commit message
12:35 tomba: tzimmermann: thanks. I'll do that now.
12:41 tomba: tzimmermann: or not. drm-misc-fixes doesn't contain the commit that needs fixing, so I think drm-misc-fixes hasn't been synced to the latest yet. is that done when the merge window closes?
12:41 tzimmermann: should not be a problem, i think.
12:41 tzimmermann: mripard ^
12:42 mripard: tzimmermann: on it
12:42 tzimmermann: great. thanks, mripard
12:44 mripard: tzimmermann: tomba: should be ok now
12:46 tzimmermann: tomba, i only see commit 3bce3fdd1ff2 in drm-next, but not in an upstream
12:46 tzimmermann: branch
12:47 tomba: tzimmermann: hmm. "git branch -r --contains 3bce3fdd1ff2" says it's in linus/master for me.
12:48 tzimmermann: tomba. ok, i see. can you add the fix to drm-misc-fixes now?
12:49 tomba: tzimmermann: no... mripard: I still don't see 3bce3fdd1ff2 in drm-misc-fixes
12:50 tzimmermann: tomba. because the bug isn't in drm-fixes yet.
12:50 tzimmermann: tomba. let me reopen drm-misc-next-fixes for you. the bug should be there and you can put the fix on top
12:50 tomba: tzimmermann: oh. ah... so many branches... =)
12:51 tzimmermann: because we need a reason to justify 3 maintainers for drm-misc :P
12:52 mripard: more like it's unacceptable for most to wait a month without applying patches :)
12:52 tzimmermann: tomba, i've reopened drm-misc-next-fixes for you. you can put the fix into this branch
12:53 tzimmermann: ping me when you're done and i'll send out the PR