On Fri, Nov 08, 2024 at 11:41:18AM +0300, Fedor Pchelkin wrote: > On Tue, 05. Nov 07:57, Greg Kroah-Hartman wrote: > > On Mon, Nov 04, 2024 at 05:55:28PM +0300, Fedor Pchelkin wrote: > > > It is just strange that the (exact same) change made by the commits is > > > duplicated by backporting tools. As it is not the first case where DRM > > > patches are involved per Greg's statement [1], I wonder if something can be > > > done on stable-team's side to avoid such odd behavior in future. > > > > No, all of this mess needs to be fixed up on the drm developer's side, > > they are the ones doing this type of crazy "let's commit the same patch > > to multiple branches and then reference a commit that will show up at an > > unknown time in the future and hope for the best!" workflow. > > > > I'm amazed it works at all, they get to keep fixing up this mess as this > > is entirely self-inflicted. > > Thanks for reply, I get your remark. DRM people are mostly CC'ed here, > hopefully it won't be that difficult to tune their established workflow to > make the stable process easier and more straightforward. > > As of now, would you mind to take the revert for 6.1? It's [PATCH 1/1] in > this thread. No point to keep it there, and the duplicated commits were > already reverted from the fresher stable kernels. > I don't see it in my review queue anymore, can you please resend it? thanks, greg k-h
