Hi Maxime, On Sat, 10 May 2025 10:43:04 +0200 Maxime Ripard <mripard@xxxxxxxxxx> wrote: > Acked-by: Maxime Ripard <mripard@xxxxxxxxxx> Thanks for looking at this series! Unfortunately the exynos patch is still needing a decision. Quick recap of the story: 1. patch was sent in v2, nobody acked/reviewed it [1] 2. was applied by mistake to drm-misc-next [2] 3. you pinged maintainers, no reply do far -> should be reverted [3] 4. Louis (fomys) asked on IRC how to handle it, no reply [4] 5. in this v3 I added a revert (patch 1), no acks/reviews on it [5] [1] https://lore.kernel.org/lkml/20250424-drm-bridge-convert-to-alloc-api-v2-14-8f91a404d86b@xxxxxxxxxxx/ [2] https://lore.kernel.org/lkml/832a9db0-cf8a-4d35-8a98-08053fbd6723@xxxxxxxxxxx/ [3] https://lore.kernel.org/lkml/20250430-arrogant-marmoset-of-justice-92ced3@houat/ [4] https://dri.freedesktop.org/~cbrill/dri-log/index.php?channel=dri-devel&highlight_names=&date=2025-05-07 [5] https://lore.kernel.org/lkml/20250509-drm-bridge-convert-to-alloc-api-v3-1-b8bc1f16d7aa@xxxxxxxxxxx/ What to do? Proposed plan: 1. Louis immediately applies the revert (patch 1) 2. I send v4 with the original patch to hopefully be reviewed/acked Plan is OK? I'm assuming Louis doesn't need an Acked/Reviewed-by for that, but I might be wrong, and we both would like to avoid further mess. This annoying issue is taking much more effort to be fixed than it took to develop it. I'd like to get past it and think about the next steps in bridge lifetime management. Thanks for your understanding. Luca -- Luca Ceresoli, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
