From: Greg KH <gregkh@linuxfoundation.org>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Kazlauskas, Nicholas" <Nicholas.Kazlauskas@amd.com>
Subject: Re: [PATCH 0/3] amdgpu DC fixes for stable
Date: Sun, 22 Sep 2019 10:14:34 +0200 [thread overview]
Message-ID: <20190922081434.GB2524798@kroah.com> (raw)
In-Reply-To: <BN6PR12MB18092E39C33B29F34E93702FF7880@BN6PR12MB1809.namprd12.prod.outlook.com>
On Fri, Sep 20, 2019 at 02:15:11PM +0000, Deucher, Alexander wrote:
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Friday, September 20, 2019 10:12 AM
> > To: Alex Deucher <alexdeucher@gmail.com>
> > Cc: stable@vger.kernel.org; Kazlauskas, Nicholas
> > <Nicholas.Kazlauskas@amd.com>; Deucher, Alexander
> > <Alexander.Deucher@amd.com>
> > Subject: Re: [PATCH 0/3] amdgpu DC fixes for stable
> >
> > On Fri, Sep 20, 2019 at 09:03:35AM -0500, Alex Deucher wrote:
> > > This set of patches is cherry-picked from 5.4 to stable to fix:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=204181
> > >
> > > Please apply!
> >
> > What stable tree(s) do you wish to see this applied to?
>
> 5.3 and 5.2 would be great. Thanks!
All queued up now, thanks.
greg k-h
prev parent reply other threads:[~2019-09-22 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 14:03 [PATCH 0/3] amdgpu DC fixes for stable Alex Deucher
2019-09-20 14:03 ` [PATCH 1/3] drm/amd/display: Allow cursor async updates for framebuffer swaps Alex Deucher
2019-09-20 14:03 ` [PATCH 2/3] drm/amd/display: Skip determining update type for async updates Alex Deucher
2019-09-20 14:03 ` [PATCH 3/3] drm/amd/display: Don't replace the dc_state for fast updates Alex Deucher
2019-09-20 14:11 ` [PATCH 0/3] amdgpu DC fixes for stable Greg KH
2019-09-20 14:15 ` Deucher, Alexander
2019-09-22 8:14 ` Greg KH [this message]
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=20190922081434.GB2524798@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Deucher@amd.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=alexdeucher@gmail.com \
--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.