From: Greg KH <greg@kroah.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: stable@vger.kernel.org, Flora Cui <Flora.Cui@amd.com>,
Junwei Zhang <Jerry.Zhang@amd.com>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] Revert "drm/amdgpu: update tile table for oland/hainan"
Date: Thu, 2 Mar 2017 20:32:56 +0100 [thread overview]
Message-ID: <20170302193256.GA20322@kroah.com> (raw)
In-Reply-To: <20170302182135.3afe11e1@endymion>
On Thu, Mar 02, 2017 at 06:21:35PM +0100, Jean Delvare wrote:
> Revert commit f8d9422ef80c ("drm/amdgpu: update tile table for
> oland/hainan") as it is causing ugly visual artifacts on at least
> Oland. This is only an optimization so we can live without it.
>
> This fixes kernel bug #194761:
> amdgpu driver breaks on Oland (SI)
> https://bugzilla.kernel.org/show_bug.cgi?id=194761
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Fixes: f8d9422ef80c ("drm/amdgpu: update tile table for oland/hainan")
> Cc: Flora Cui <Flora.Cui@amd.com>
> Cc: Junwei Zhang <Jerry.Zhang@amd.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> ---
> Note: This is for stable v4.10 branch only. v4.11 and later have a
> different fix, but it's much larger and more intrusive so not suitable
> for a stable branch.
>
> drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c | 330 ++++++++++++++--------------------
> 1 file changed, 139 insertions(+), 191 deletions(-)
More intrusive than this? I'd much rather take what is in 4.11 than
have you make a huge change like this if at all possible.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-02 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 17:21 [PATCH] Revert "drm/amdgpu: update tile table for oland/hainan" Jean Delvare
2017-03-02 17:58 ` Deucher, Alexander
2017-03-02 19:32 ` Greg KH [this message]
2017-03-02 21:04 ` Jean Delvare
2017-03-02 21:23 ` Deucher, Alexander
2017-03-12 19:17 ` Patch "Revert "drm/amdgpu: update tile table for oland/hainan"" has been added to the 4.10-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=20170302193256.GA20322@kroah.com \
--to=greg@kroah.com \
--cc=Flora.Cui@amd.com \
--cc=Jerry.Zhang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=jdelvare@suse.de \
--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.