From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, airlied@redhat.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: [PULL] vmwgfx-next
Date: Fri, 28 Mar 2014 14:35:16 +0100 [thread overview]
Message-ID: <1396013716-14354-1-git-send-email-thellstrom@vmware.com> (raw)
Dave,
vmwgfx render-node support and drm + ttm changes it depends upon.
The following changes since commit 60f2b4af1258c05e6b037af866be81abc24438f7:
drm/i915: fix build warning on 32-bit (v2) (2014-03-28 13:40:48 +1000)
are available in the git repository at:
git://people.freedesktop.org/~thomash/linux tags/vmwgfx-next-2014-03-28
for you to fetch changes up to 03c5b8f077218bec50f1355b76dea405a7112878:
drm/vmwgfx: Bump driver minor and date (2014-03-28 14:19:05 +0100)
----------------------------------------------------------------
Pull request of 2014-03-28
----------------------------------------------------------------
Thomas Hellstrom (16):
drm: Have the crtc code only reference master from legacy nodes v2
drm: Break out ioctl permission check to a separate function v2
drm: Make control nodes master-less v3
drm: Improve on minor type helpers v3
drm: Remove the minor master list
drm: Protect the master management with a drm_device::master_mutex v3
drm: Add a function to get the ioctl flags
drm/vmwgfx: Use a per-device semaphore for reservation protection
drm/vmwgfx: Reinstate and tighten security around legacy master model
drm/vmwgfx: Drop authentication requirement on UNREF ioctls
drm/vmwgfx: Allow prime fds in the surface reference ioctls
drm/vmwgfx: Tighten security around surface sharing v2
drm/ttm: Add a ttm_ref_object_exists function
drm/vmwgfx: Tighten the security around buffer maps
drm/vmwgfx: Enable render nodes
drm/vmwgfx: Bump driver minor and date
drivers/gpu/drm/drm_crtc.c | 14 +--
drivers/gpu/drm/drm_drv.c | 132 +++++++++++++++++++--------
drivers/gpu/drm/drm_fops.c | 26 +++---
drivers/gpu/drm/drm_stub.c | 48 +++++-----
drivers/gpu/drm/ttm/ttm_object.c | 46 ++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 5 +-
drivers/gpu/drm/vmwgfx/vmwgfx_dmabuf.c | 15 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 143 +++++++++++++++++++++++-------
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 9 +-
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 5 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 9 +-
drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c | 10 +--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 15 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 24 ++---
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 5 +-
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 143 +++++++++++++++++++++---------
include/drm/drmP.h | 61 ++++++++-----
include/drm/ttm/ttm_object.h | 4 +
include/uapi/drm/vmwgfx_drm.h | 12 ++-
19 files changed, 500 insertions(+), 226 deletions(-)
next reply other threads:[~2014-03-28 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 13:35 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-04 6:19 [PULL] vmwgfx-next Thomas Hellstrom
2014-07-04 10:44 Thomas Hellstrom
2014-12-03 9:01 Thomas Hellstrom
2015-03-11 19:02 Thomas Hellstrom
2015-04-01 19:33 ` Thomas Hellstrom
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=1396013716-14354-1-git-send-email-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@vmware.com \
/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