From: Deepak Singh Rawat <drawat@vmware.com>
To: "airlied@linux.ie" <airlied@linux.ie>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: Deepak Singh Rawat <drawat@vmware.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>
Subject: [GIT PULL] drm/vmwgfx: vmwgfx-next
Date: Tue, 9 Apr 2019 19:49:07 +0000 [thread overview]
Message-ID: <20190409194917.19096-1-drawat@vmware.com> (raw)
Hi Daniel/Dave,
The vmwgfx-next changes for 5.2:
Resource dirtying improvement by Thomas,
user-space error logging improvement and
some other minor fixes.
The following changes since commit 14d2bd53a47a7e1cb3e03d00a6b952734cf90f3f:
Merge tag 'drm-misc-next-2019-04-04' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2019-04-05 11:38:02 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drawat/linux.git vmwgfx-next
for you to fetch changes up to c601b12fb634e2d0c2669706b38dba98a3c3a832:
drm/vmwgfx: Remove set but not used variable 'fb_offset, fb_depth' (2019-04-08 10:29:05 -0700)
----------------------------------------------------------------
Chengguang Xu (1):
drm/vmwgfx: remove redundant unlikely annotation
Deepak Rawat (8):
drm/vmwgfx: Use preprocessor macro to get valid context node
drm/vmwgfx: Use preprocessor macro for cmd struct
drm/vmwgfx: Add a new define for vmwgfx user-space debugging
drm/vmwgfx: Print message when command verifier returns with error
drm/vmwgfx: Clean up some debug messages in vmwgfx_execbuf.c
drm/vmwgfx: Use VMW_DEBUG_USER for device command buffer errors
drm/vmwgfx: Fix formatting and spaces in vmwgfx_execbuf.c
drm/vmwgfx: Use preprocessor macro for FIFO allocation
Nathan Chancellor (1):
drm/vmwgfx: Zero initialize handle in vmw_execbuf_process
Thomas Hellstrom (1):
drm/vmwgfx: Be more restrictive when dirtying resources
YueHaibing (2):
drm/vmwgfx: Remove set but not used variable 'restart'
drm/vmwgfx: Remove set but not used variable 'fb_offset, fb_depth'
drivers/gpu/drm/vmwgfx/vmwgfx_binding.c | 98 +++++----
drivers/gpu/drm/vmwgfx/vmwgfx_binding.h | 2 +
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 24 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 59 ++----
drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c | 23 +--
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 29 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 1505 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------------------
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 4 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 27 +--
drivers/gpu/drm/vmwgfx/vmwgfx_gmr.c | 9 +-
drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c | 12 +-
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 28 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 6 +-
drivers/gpu/drm/vmwgfx/vmwgfx_mob.c | 25 +--
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | 4 +-
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 28 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 23 +--
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 44 ++---
drivers/gpu/drm/vmwgfx/vmwgfx_simple_resource.c | 12 +-
drivers/gpu/drm/vmwgfx/vmwgfx_so.c | 45 +++--
drivers/gpu/drm/vmwgfx/vmwgfx_so.h | 1 +
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 47 ++---
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 80 +++-----
drivers/gpu/drm/vmwgfx/vmwgfx_validation.c | 61 ++++--
drivers/gpu/drm/vmwgfx/vmwgfx_validation.h | 7 +
25 files changed, 972 insertions(+), 1231 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-04-09 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 19:49 Deepak Singh Rawat [this message]
2019-04-19 17:36 ` [GIT PULL] drm/vmwgfx: vmwgfx-next Deepak Singh Rawat
2019-04-23 20:55 ` Dave Airlie
2019-04-23 21:00 ` Deepak Singh Rawat
2019-04-23 21:08 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2019-04-23 21:16 Deepak Rawat
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=20190409194917.19096-1-drawat@vmware.com \
--to=drawat@vmware.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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