On Mon, Jun 29, 2026 at 3:57 PM Robert Mader <[email protected]> wrote: > > Hi Mikhail, > > thanks for the quick review! And no worries, I was very happy about your > patch, which is why I looked deeper into it in the first place. > > Given the patch fixes a newly introduced regression (and is very > simple), do you think there's a chance to still get it into 7.1 - or > would it need to go via the usual 7.2/7.3 release schedule + backport?
Hi Robert, The timing depends on Vivek and the drm-misc maintainers, not me, but here's the situation as I understand it: The original commit 504e2b4ab97a only landed in 7.2 (it went into drm-misc-next, not drm-misc-fixes). So 7.1 was never affected by the regression -- there's nothing to fix there. For 7.2: since your patch fixes a regression introduced in the same cycle, it would ideally go through drm-misc-fixes to land in 7.2 before release, avoiding a broken commit in the final tree. That's the cleanest outcome. Adding Vivek -- he pushed the original patch and would know whether drm-misc-fixes is the right route at this point in the cycle. -- Thanks, Mikhail
