Computer Enthusiastic
2023-Jan-28 14:49 UTC
[Nouveau] [PATCH] nouveau: explicitly wait on the fence in nouveau_bo_move_m2mf
Hello, The patch "[Nouveau] [PATCH] nouveau: explicitly wait on the fence in nouveau_bo_move_m2mf" [1] was marked for kernels v5.15+ and it was merged upstream. The same patch [1] works with kernel 5.10.y, but it is not been merged upstream so far. According to Karol Herbst suggestion [2], I'm sending this message to ask for merging it into 5.10 kernel. Thanks in advance. --- [1] https://lore.kernel.org/nouveau/20220819200928.401416-1-kherbst at redhat.com/ [2] https://lore.kernel.org/nouveau/CACO55tv0jO2TmuWcwFiAUQB-__DZVwhv7WNN9MfgMXV053gknw at mail.gmail.com/
Greg KH
2023-Jan-28 17:51 UTC
[Nouveau] [PATCH] nouveau: explicitly wait on the fence in nouveau_bo_move_m2mf
On Sat, Jan 28, 2023 at 03:49:59PM +0100, Computer Enthusiastic wrote:> Hello, > > The patch "[Nouveau] [PATCH] nouveau: explicitly wait on the fence in > nouveau_bo_move_m2mf" [1] was marked for kernels v5.15+ and it was merged > upstream. > > The same patch [1] works with kernel 5.10.y, but it is not been merged > upstream so far. > > According to Karol Herbst suggestion [2], I'm sending this message to ask > for merging it into 5.10 kernel.We need to know the git commit id. And have you tested it on 5.10.y? And why are you stuck on 5.10.y for this type of hardware? Why not move to 5.15.y or 6.1.y? And as my bot says: <formletter> This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for how to do this properly. </formletter> thanks, greg k-h