From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:55974 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729847AbeHPSx1 (ORCPT ); Thu, 16 Aug 2018 14:53:27 -0400 Date: Thu, 16 Aug 2018 17:54:04 +0200 From: Greg KH To: Michel =?iso-8859-1?Q?D=E4nzer?= Cc: stable@vger.kernel.org Subject: Re: Nomination of amdgpu fixes for stable backport Message-ID: <20180816155404.GC18296@kroah.com> References: <20180816152043.GI10648@kroah.com> <26922983-6ffc-e184-0e1e-3a205e21a4e4@daenzer.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <26922983-6ffc-e184-0e1e-3a205e21a4e4@daenzer.net> Sender: stable-owner@vger.kernel.org List-ID: 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? thanks, greg k-h