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-fixes-4.19
Date: Thu, 4 Oct 2018 11:52:54 -0400 [thread overview]
Message-ID: <1538668374-22334-1-git-send-email-alexander.deucher@amd.com> (raw)
Hi Dave,
Just two small fixes for 4.19:
- Fix an ordering issue in DC with respect to atomic flips that could result
in a crash
- Fix incorrect use of process->mm in KFD
The following changes since commit d8938c981f58ee344687b7910a611ac345960045:
Merge branch 'drm-tda9950-fixes' of git://git.armlinux.org.uk/~rmk/linux-arm into drm-fixes (2018-10-04 10:32:14 +1000)
are available in the git repository at:
git://people.freedesktop.org/~agd5f/linux drm-fixes-4.19
for you to fetch changes up to 11b29c9e25788d0afb2ddb67bcd89424bd25f2f7:
drm/amdkfd: Fix incorrect use of process->mm (2018-10-04 11:37:25 -0400)
----------------------------------------------------------------
Felix Kuehling (1):
drm/amdkfd: Fix incorrect use of process->mm
Shirish S (1):
drm/amd/display: Signal hw_done() after waiting for flip_done()
.../gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 37 +++++++++++++++++-----
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 10 ++++--
2 files changed, 37 insertions(+), 10 deletions(-)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2018-10-04 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 15:52 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-27 15:54 [pull] amdgpu drm-fixes-4.19 Alex Deucher
2018-09-20 15:58 Alex Deucher
2018-09-12 15:47 Alex Deucher
2018-08-29 20:25 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=1538668374-22334-1-git-send-email-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;
as well as URLs for NNTP newsgroup(s).