dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Sinclair Yeh <syeh@vmware.com>
To: airlied@redhat.com, airlied@gmail.com
Cc: linux-graphics-maintainer@vmware.com, dri-devel@lists.freedesktop.org
Subject: [git pull] vmwgfx-fixes
Date: Fri, 21 Jul 2017 16:57:57 +0200	[thread overview]
Message-ID: <20170721145756.GA123002@ubuntu> (raw)

Hi Dave,

The following changes since commit 9ff1beb1d19ffe2b26bf9cd2d33e6073d4f4b5fe:

  Merge tag 'drm-intel-fixes-2017-06-27' of git://anongit.freedesktop.org/git/drm-intel into drm-fixes (2017-06-28 17:07:15 +1000)

are available in the git repository at:

  git://people.freedesktop.org/~syeh/repos_linux drm-vmwgfx-fixes

for you to fetch changes up to 8046306fb9dedf216fc37a7dadc0e35ce37e9567:

  drm/vmwgfx: constify pci_device_id. (2017-07-17 23:41:22 -0700)

----------------------------------------------------------------
Arvind Yadav (2):
      drm/vmwgfx: dma-buf: Constify ttm_place structures.
      drm/vmwgfx: constify pci_device_id.

Brian Paul (1):
      drm/vmwgfx: fix comment mistake for vmw_cmd_dx_set_index_buffer()

Christophe JAILLET (1):
      drm/vmwgfx: Fix handling of errors returned by 'vmw_cotable_alloc()'

Ravikant B Sharma (1):
      drm/vmwgfx: Fix NULL pointer comparison

Sinclair Yeh (3):
      drm/vmwgfx: Limit max desktop dimensions to 8Kx8K
      drm/vmwgfx: Fix cursor hotspot issue with Wayland on Fedora
      drm/vmwgfx: Fix gcc-7.1.1 warning

Souptick Joarder (1):
      drm/vmwgfx: Use dma_pool_zalloc

 drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c        | 24 ++++++++++++------------
 drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c        | 10 ++++------
 drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf_res.c    |  4 ++--
 drivers/gpu/drm/vmwgfx/vmwgfx_context.c       |  6 +++---
 drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c       |  2 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c           |  8 ++++----
 drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c       |  8 ++++----
 drivers/gpu/drm/vmwgfx/vmwgfx_fence.c         | 10 +++++-----
 drivers/gpu/drm/vmwgfx/vmwgfx_gmrid_manager.c |  2 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_kms.c           |  9 +++++++++
 drivers/gpu/drm/vmwgfx/vmwgfx_mob.c           |  6 +++---
 drivers/gpu/drm/vmwgfx/vmwgfx_msg.c           |  6 +++---
 drivers/gpu/drm/vmwgfx/vmwgfx_resource.c      |  4 ++--
 drivers/gpu/drm/vmwgfx/vmwgfx_shader.c        |  6 +++---
 drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c          |  4 ++--
 15 files changed, 58 insertions(+), 51 deletions(-)

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-07-21 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 14:57 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-01-23 18:05 [git pull] vmwgfx-fixes Sinclair Yeh
2016-12-14  2:46 Sinclair Yeh
2016-10-17 18:55 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=20170721145756.GA123002@ubuntu \
    --to=syeh@vmware.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@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).