summaryrefslogtreecommitdiffstats
path: root/Kbuild
diff options
context:
space:
mode:
authorDave Airlie <airlied@redhat.com>2014-01-14 01:55:36 +0100
committerDave Airlie <airlied@redhat.com>2014-01-14 01:55:36 +0100
commitfaf096ffba2b1a4066e6d6dcd1243cc5f3d1fb23 (patch)
tree4793c625d9eaae10f453b8c4d32543de86875402 /Kbuild
parentMerge tag 'ttm-next-2014-01-13' of git://people.freedesktop.org/~thomash/linu... (diff)
parentdrivers: gpu: Mark functions as static in vmwgfx_fence.c (diff)
downloadlinux-faf096ffba2b1a4066e6d6dcd1243cc5f3d1fb23.tar.xz
linux-faf096ffba2b1a4066e6d6dcd1243cc5f3d1fb23.zip
Merge tag 'vmwgfx-next-2014-01-13' of git://people.freedesktop.org/~thomash/linux into drm-next
Anyway, nothing big here, Three more code cleanup patches from Rashika Kheria, and one TTM/vmwgfx patch from me that tightens security around TTM objects enough for them to opened using prime objects from render nodes: Previously any client could access a shared buffer using the "name", also without actually opening it. Now a reference is required, and for render nodes such a reference is intended to only be obtainable using a prime fd. vmwgfx-next 2014-01-13 pull request * tag 'vmwgfx-next-2014-01-13' of git://people.freedesktop.org/~thomash/linux: drivers: gpu: Mark functions as static in vmwgfx_fence.c drivers: gpu: Mark functions as static in vmwgfx_buffer.c drivers: gpu: Mark functions as static in vmwgfx_kms.c drm/ttm: ttm object security fixes for render nodes
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions