From: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org>
Subject: [pull] amdgpu drm-next-4.16
Date: Wed, 7 Feb 2018 14:15:18 -0500 [thread overview]
Message-ID: <20180207191518.15417-1-alexander.deucher@amd.com> (raw)
Hi Dave,
Just one fix this week for 4.16. This is on top of the pull request I
sent last week. One of the fixes from last week got applied to the wrong
asic by accident. The patch this week fixes that.
The following changes since commit 7e24a3ea825e546487c3fc47f8cbf6512f6c9e8c:
drm/amdgpu: disable coarse grain clockgating for ST (2018-01-29 23:30:44 -0500)
are available in the git repository at:
git://people.freedesktop.org/~agd5f/linux drm-next-4.16
for you to fetch changes up to fb4bbba2775399149ca902f31eb5c46cc7a8d8b8:
drm/amdgpu: re-enable CGCG on CZ and disable on ST (2018-02-06 00:05:22 -0500)
----------------------------------------------------------------
Shirish S (1):
drm/amdgpu: re-enable CGCG on CZ and disable on ST
drivers/gpu/drm/amd/amdgpu/vi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2018-02-07 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 19:15 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-15 20:49 [pull] amdgpu drm-next-4.16 Alex Deucher
2018-01-24 21:10 Alex Deucher
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=20180207191518.15417-1-alexander.deucher@amd.com \
--to=alexdeucher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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