From: Greg KH <gregkh@linuxfoundation.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: stable@vger.kernel.org
Subject: Re: Nomination of amdgpu fixes for stable backport
Date: Wed, 12 Sep 2018 11:02:45 +0200 [thread overview]
Message-ID: <20180912090245.GA767@kroah.com> (raw)
In-Reply-To: <0ff704b0-8731-b040-c82e-090f21ca190d@daenzer.net>
On Wed, Sep 12, 2018 at 10:39:56AM +0200, Michel D�nzer wrote:
>
> 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.
Ah, our emails crossed. I just tried to apply these, but the original
ones all failed to apply :(
And I normally wait for the drm patches to go "last" for the stable
trees due to all of the merge issues they normally cause, like this :(
greg k-h
next prev parent reply other threads:[~2018-09-12 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 7:53 Nomination of amdgpu fixes for stable backport Michel Dänzer
2018-08-16 15:20 ` Greg KH
2018-08-16 15:36 ` Michel Dänzer
2018-08-16 15:54 ` Greg KH
2018-08-16 16:16 ` Michel Dänzer
2018-09-12 8:39 ` Michel Dänzer
2018-09-12 9:02 ` Greg KH [this message]
2018-09-12 8:55 ` Greg KH
2018-09-12 9:11 ` Michel Dänzer
2018-09-12 9:16 ` Greg KH
2018-09-12 9:28 ` Michel Dänzer
2018-09-12 18:43 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180912090245.GA767@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=michel@daenzer.net \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox