16:53 <DavidHeidelberg[m]> robclark hello! Thanks for pushing mine drm/msm/mdp4 fixes. Is there chance while they're in `-next` you could append `Cc: <stable@vger.kernel.org> # 5.10.x` which I didn't realized it would be nice to have when I was sending them?

16:54 <DavidHeidelberg[m]> sharing their sha's here, but if you want I can mail it to you :) : 4d319afe666b0fc9a9855ba9bdf9ae3710ecf431 4af4fc92939dc811ef291c0673946555aa4fb71f 56bd931ae506730c9ab1e4cc4bfefa43fc2d18fa

16:58 <robclark> DavidHeidelberg[m]: I try to avoid force-pushing once they are in msm-next since we have downstream product kernel trees cherry-picking from msm-next, and force-push changes the commit-sha's.. But I think there is a process to nominate stable backports (probably just send to stable@ and mention the upstream commit sha? I'd have to check the docs)

16:59 <DavidHeidelberg[m]> robclark it's preferable to have it already as option 1 (Cc:) but I can do it afterwards after getting into Linus tree (opt. 2 or 3) https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

17:07 <bamse> Marijn[m]: i think i've sent them since we spoke last, but i got some feedback right before the last merge window that i haven't followed up on

17:08 <bamse> Marijn[m]: i think i did the changes, but i've not gotten back to send it out...picked it up last week to do so, but got side tracked by a cold, hoping to get it out this week

21:57 <Marijn[m]> bamse: Yeah that's what I recall as well. Get well soon, I'll try to test+review them ASAP one last time when you send them, thanks!