From: Oded Gabbay <oded.gabbay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [git pull] amdkfd next 4.18
Date: Mon, 28 May 2018 14:04:35 +0300 [thread overview]
Message-ID: <20180528110435.GA17960@odedg-x270> (raw)
Hi Dave,
Final amdkfd pull request for 4.18:
- Build amdkfd's related files inside amdgpu only if amdkfd is built
- Fix compile warning
- Print info message in case ASIC is not supported by amdkfd
Thanks,
Oded
The following changes since commit dd41fb8547c2422f3a3a75e7226525e8bba9381c:
Merge branch 'drm-next-4.18' of git://people.freedesktop.org/~agd5f/linux into drm-next (2018-05-25 10:28:33 +1000)
are available in the Git repository at:
git://people.freedesktop.org/~gabbayo/linux tags/drm-amdkfd-next-2018-05-28
for you to fetch changes up to ebe1d22b57b86b6739f2739b5a0f52435596d84d:
drm/amdgpu: fix 32-bit build warning (2018-05-25 17:50:09 +0200)
----------------------------------------------------------------
Arnd Bergmann (1):
drm/amdgpu: fix 32-bit build warning
Oded Gabbay (1):
drm/amdgpu: conditionally compile amdgpu's amdkfd files
Tom Stellard (1):
drm/amdgpu: Use dev_info() to report amdkfd is not supported for this ASIC
drivers/gpu/drm/amd/amdgpu/Makefile | 13 ++++--
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 49 ++++++++++++++++++++++-
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 12 +++---
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c | 4 +-
4 files changed, 66 insertions(+), 12 deletions(-)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2018-05-28 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 11:04 Oded Gabbay [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-14 7:01 [git pull] amdkfd next 4.18 Oded Gabbay
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=20180528110435.GA17960@odedg-x270 \
--to=oded.gabbay-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@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).