From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Christian Koenig <christian.koenig@amd.com>,
Grigori Goronzy <greg@chown.ath.cx>,
"for 3.8" <stable@vger.kernel.org>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] drm/amdgpu: fix regression on CIK (v2)
Date: Sun, 10 Apr 2016 09:22:47 -0700 [thread overview]
Message-ID: <20160410162247.GB2697@kroah.com> (raw)
In-Reply-To: <CADnq5_PeMJ2ka9n2pDo6NmimxRe63qwwTjWRqtqSgpD6Mn6JVw@mail.gmail.com>
On Tue, Mar 22, 2016 at 04:31:30PM -0400, Alex Deucher wrote:
> On Tue, Mar 22, 2016 at 4:27 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Mar 22, 2016 at 04:14:30PM -0400, Alex Deucher wrote:
> >> On Tue, Mar 22, 2016 at 4:11 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> > 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.
> >>
> >> It's correct as is for 4.6. I cherry-picked it out of my drm-next
> >> tree into 4.5 since it was a bug fix, but missed the internal driver
> >> structure change in drm-next that was not in 4.5.
> >
> > I'm sorry, I don't understand at all what you mean here :(
> >
> > What changed between 4.5.0 and 4.6-rc1 that made 4.5 "broken"? What
> > fixed it in 4.6-rc1?
>
> The patch was written and tested against drm-next, but I cherry-picked
> it to 4.5 as is since it was a bug fix. However, I missed the
> internal driver structure change that it depended on. Now that
> drm-next has been merged into 4.6 (including the driver structure
> change), the code from 4.5 works fine. However 4.5 and older kernels
> are broken since they don't have the changes for 4.6.
I still don't understand. What is the commit in Linus's tree that
matches this change? Why can't I just cherry-pick that patch instead of
this "custom" one?
thanks,
greg k-h
next prev parent reply other threads:[~2016-04-10 16:22 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
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 [this message]
[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=20160410162247.GB2697@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).