From: Oded Gabbay <oded.gabbay@gmail.com>
To: airlied@gmail.com
Cc: dri-devel@lists.freedesktop.org
Subject: [git pull] drm-amdkfd-fixes 4.14
Date: Sun, 24 Sep 2017 14:26:28 +0300 [thread overview]
Message-ID: <20170924112628.GA675@odedg-x260> (raw)
Hi Dave,
This is amdkfd pull request for 4.14-rc3.
It contains the following fixes:
- correct checking of return value
- send correct parameter to function (According to the parameter type)
- avoid spamming of dmesg log
- fix queue wrapping calculations
Thanks,
Oded
The following changes since commit 56eac98b8a0bbb72132340dbfedc912c68c4bd56:
Merge tag 'exynos-drm-fixes-for-v4.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-fixes (2017-09-21 08:02:39 +1000)
are available in the git repository at:
git://people.freedesktop.org/~gabbayo/linux tags/drm-amdkfd-fixes-2017-09-24
for you to fetch changes up to d42818354081b0805872f4a11c16778a8fbe53ac:
drm/amdkfd: Print event limit messages only once per process (2017-09-24 14:10:26 +0300)
----------------------------------------------------------------
Colin Ian King (1):
drm/amdkfd: check for null dev to avoid a null pointer dereference
Felix Kuehling (2):
drm/amdkfd: Fix incorrect destroy_mqd parameter
drm/amdkfd: Print event limit messages only once per process
Yong Zhao (1):
drm/amdkfd: Fix kernel-queue wrapping bugs
drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 2 ++
drivers/gpu/drm/amd/amdkfd/kfd_events.c | 5 ++++-
drivers/gpu/drm/amd/amdkfd/kfd_kernel_queue.c | 20 ++++++++++++++++----
drivers/gpu/drm/amd/amdkfd/kfd_priv.h | 1 +
4 files changed, 23 insertions(+), 5 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2017-09-24 11:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170924112628.GA675@odedg-x260 \
--to=oded.gabbay@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.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