From: Sinclair Yeh <syeh@vmware.com>
To: airlied@redhat.com
Cc: thellstrom@vmware.com, dri-devel@lists.freedesktop.org
Subject: [git pull] vmwgfx-fixes
Date: Mon, 17 Oct 2016 11:55:07 -0700 [thread overview]
Message-ID: <20161017185507.GA33718@promb-2n-dhcp370.eng.vmware.com> (raw)
Hi Dave,
The following changes since commit 90fd68dcf9a763f7e575c8467415bd8a66d073f4:
drm/udl: fix line iterator in damage handling (2016-09-28 13:29:18 +1000)
are available in the git repository at:
ssh://people.freedesktop.org/~syeh/repos_linux drm-vmwgfx-fixes
for you to fetch changes up to 862f6157d176c9db5a7ed423245108d9bb3d7038:
drm/vmwgfx: Adjust checks for null pointers in 13 functions (2016-10-10 13:23:16 -0700)
----------------------------------------------------------------
Baole Ni (1):
drm/vmwgfx: Replace numeric parameter like 0444 with macro
Charmaine Lee (1):
drm/vmwgfx: Enable SVGA_3D_CMD_DX_TRANSFER_FROM_BUFFER command
Chris Wilson (1):
drm/vmwgfx: Remove call to reservation_object_test_signaled_rcu before wait
Markus Elfring (3):
drm/vmwgfx: Use kmalloc_array() in vmw_surface_define_ioctl()
drm/vmwgfx: Use memdup_user() rather than duplicating its implementation
drm/vmwgfx: Adjust checks for null pointers in 13 functions
Thomas Hellstrom (4):
drm/vmwgfx: Allow resource relocations on byte boundaries
drm/vmwgfx: Remove a leftover debug printout
drm/vmwgfx: Limit the user-space command buffer size
drm/vmwgfx: Avoid validating views on view destruction
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 10 +++----
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 145 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 6 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 56 ++++++++++++++++----------------------
5 files changed, 146 insertions(+), 73 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-10-17 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:55 Sinclair Yeh [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-03 17:26 [Git PULL] vmwgfx-fixes Sinclair Yeh
2017-08-29 21:25 Sinclair Yeh
2017-07-21 14:57 [git pull] vmwgfx-fixes Sinclair Yeh
2017-01-23 18:05 Sinclair Yeh
2016-12-14 2:46 Sinclair Yeh
2016-07-08 15:57 Sinclair Yeh
2016-07-04 15:13 Sinclair Yeh
2016-07-08 3:34 ` Dave Airlie
2016-04-28 20:02 Sinclair Yeh
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=20161017185507.GA33718@promb-2n-dhcp370.eng.vmware.com \
--to=syeh@vmware.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@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;
as well as URLs for NNTP newsgroup(s).