summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorDave Airlie <airlied@redhat.com>2015-08-14 10:15:24 +1000
committerDave Airlie <airlied@redhat.com>2015-08-14 10:15:24 +1000
commit8f9cb50789e76f3e224e8861adf650e55c747af4 (patch)
treefa84fd7daf1a6dd252f2632cb33b634cb9784691 /MAINTAINERS
parente1474e7bdf6b16db41cc12b8e7b3fefd8668f3cf (diff)
parenta63c580a5271b61f12cf91e768120e33792e2907 (diff)
downloadlinux-stable-8f9cb50789e76f3e224e8861adf650e55c747af4.tar.gz
linux-stable-8f9cb50789e76f3e224e8861adf650e55c747af4.tar.bz2
linux-stable-8f9cb50789e76f3e224e8861adf650e55c747af4.zip
Merge tag 'drm-amdkfd-next-fixes-2015-08-05' of git://people.freedesktop.org/~gabbayo/linux into drm-next
Two small bug fixes for the code you pulled for 4.3: - Used a SHIFT define instead of a MASK define to check if a bit is turned on when destroying hqd. Luckily, this is in gfx7 interface file with amdgpu, which was used only for bring-up purposes of amdgpu, so no real effect on a running system - Used a logical AND instead of a bitwise AND operator, when initializing sdma virtual memory when using SDMA queues * tag 'drm-amdkfd-next-fixes-2015-08-05' of git://people.freedesktop.org/~gabbayo/linux: drm/amdkfd: fix bug when initializing sdma vm drm/amdgpu: fix bug when amdkfd destroys hqd
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions