Hi Greg, On 2018-08-16 5:54 p.m., Greg KH wrote: > On Thu, Aug 16, 2018 at 05:36:16PM +0200, Michel Dänzer wrote: >> On 2018-08-16 05:20 PM, Greg KH wrote: >>> On Thu, Aug 16, 2018 at 09:53:54AM +0200, Michel Dänzer wrote: >>>> >>>> Hi stable kernel maintainers, >>>> >>>> >>>> please squash these amdgpu fixes together and backport them to all >>>> applicable stable branches: >>> >>> Nothing gets squashed, we apply individual patches :) >> >> That's a bit unfortunate in this case, as there can be spurious WARN >> splats with only the first fix. > > That's fine, no one is going to only apply one of them. > >>>> 15e6b76880e65be24250e30986084b5569b7a06f "drm/amdgpu: Warn and update >>>> pin_size values when >>>> destroying a pinned BO" >>>> 456607d816d89a442a3d5ec98b02c8bc950b5228 "drm/amdgpu: Don't warn on >>>> destroying a pinned BO" >>>> >>>> (These depend on commits a5ccfe5c20740f2fbf00291490cdf8d2373ec255 and >>>> ddc21af4d0f37f42b33c54cb69b215997fe5b082, which already have Cc: stable) >>> >>> What stable tree(s) do you want these applied to? >> >> All active trees where they apply (and so do the patches they depend on). > > A hint might be nice here, what trees did you test this on? Is there a reason why these 4 fixes haven't been backported yet? People are running into the issues fixed by them. There seem to be many other fixes under drivers/gpu/drm/ with Cc: stable which haven't been backported yet. Thanks, -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
