All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
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 10:55:08 +0200	[thread overview]
Message-ID: <20180912085508.GA24353@kroah.com> (raw)
In-Reply-To: <a49d6e0c-147d-9aae-0c17-172a8b4182b4@daenzer.net>

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:
> 
> 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)

Those commits did not apply to the stable tree, so can you please send a
series of patches that do apply so that I can queue all of these up
properly?

thanks,

greg k-h

  parent reply	other threads:[~2018-09-12 13:58 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
2018-09-12  8:55 ` Greg KH [this message]
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=20180912085508.GA24353@kroah.com \
    --to=greg@kroah.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.