From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: christian.koenig@amd.com, greg@chown.ath.cx,
stable@vger.kernel.org, Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] drm/amdgpu: fix regression on CIK (v2)
Date: Tue, 22 Mar 2016 16:11:20 -0400 [thread overview]
Message-ID: <20160322201120.GA28527@kroah.com> (raw)
In-Reply-To: <1458676098-9543-1-git-send-email-alexander.deucher@amd.com>
On Tue, Mar 22, 2016 at 03:48:18PM -0400, Alex Deucher wrote:
> From: Grigori Goronzy <greg@chown.ath.cx>
>
> This fix was written against drm-next, but when it was
> backported to 4.5 as a stable fix, the driver internal
> structure change was missed. Fix that up here to avoid
> a hang due to waiting for the wrong sequence number.
>
> v2: agd: fix up commit message
>
> Signed-off-by: Grigori Goronzy <greg@chown.ath.cx>
> Cc: stable@vger.kernel.org
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
>
> Hi Greg,
>
> The code is correct for 4.6, this fix should be applied to
> 4.5 and older stable kernels.
What is the patch in 4.6 that made it "correct"? I would much rather
take that than something else.
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-22 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 19:48 [PATCH] drm/amdgpu: fix regression on CIK (v2) Alex Deucher
2016-03-22 20:11 ` Greg KH [this message]
2016-03-22 20:14 ` Alex Deucher
2016-03-22 20:27 ` Greg KH
2016-03-22 20:31 ` Alex Deucher
2016-04-10 16:22 ` Greg KH
[not found] ` <570B5068.90302@amd.com>
2016-04-25 17:21 ` Alex Deucher
2016-04-25 22:49 ` Ben Hutchings
2016-05-01 22:59 ` Patch "drm/amdgpu: fix regression on CIK (v2)" has been added to the 4.4-stable tree gregkh
2016-05-01 22:59 ` Patch "drm/amdgpu: fix regression on CIK (v2)" has been added to the 4.5-stable tree gregkh
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=20160322201120.GA28527@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=christian.koenig@amd.com \
--cc=greg@chown.ath.cx \
--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.