All of lore.kernel.org
 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-next
Date: Mon, 28 Aug 2017 22:22:37 +0200	[thread overview]
Message-ID: <20170828202237.GA4229@ubuntu> (raw)

Hi Dave,

The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f:

  Merge branch 'linux-4.14' of git://github.com/skeggsb/linux into drm-next (2017-08-23 05:32:26 +1000)

are available in the git repository at:

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

for you to fetch changes up to d78acfe934e3b9f533f72ee3dde0982935fc2b32:

  drm/vmwgfx: Bump the version for fence FD support (2017-08-28 17:53:32 +0200)

----------------------------------------------------------------
Sinclair Yeh (4):
      drm/vmwgfx: Prepare to support fence fd
      drm/vmwgfx: Add support for imported Fence File Descriptor
      drm/vmwgfx: Add export fence to file descriptor support
      drm/vmwgfx: Bump the version for fence FD support

Thomas Hellstrom (5):
      drm/vmwgfx: Don't use drm_irq_[un]install
      drm/vmwgfx: Move irq bottom half processing to threads
      drm/vmwgfx: Restart command buffers after errors
      drm/vmwgfx: Support the NOP_ERROR command
      drm/vmwgfx: Fix incorrect command header offset at restart

 drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c  | 242 ++++++++++++++++++++++++++++++++++++++++++++----------------
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c     |  11 +--
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h     |  39 ++++++----
 drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 148 +++++++++++++++++++++++++++++++++----
 drivers/gpu/drm/vmwgfx/vmwgfx_fence.c   | 104 +++++++++++++++++---------
 drivers/gpu/drm/vmwgfx/vmwgfx_fence.h   |   4 +
 drivers/gpu/drm/vmwgfx/vmwgfx_irq.c     | 111 +++++++++++++++++++++++-----
 drivers/gpu/drm/vmwgfx/vmwgfx_kms.c     |   2 +-
 include/uapi/drm/vmwgfx_drm.h           |  11 ++-
 9 files changed, 511 insertions(+), 161 deletions(-)

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

             reply	other threads:[~2017-08-28 20:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 20:22 Sinclair Yeh [this message]
2017-08-28 20:35 ` [Git PULL] vmwgfx-next Dave Airlie
2017-08-28 20:39   ` Sinclair Yeh
  -- strict thread matches above, loose matches on Subject: below --
2020-01-16  9:29 [git pull] vmwgfx-next Thomas Hellström (VMware)
2020-01-20 21:09 ` Dave Airlie
2020-01-20 21:42   ` Thomas Hellström (VMware)
2020-01-21  9:49   ` Thomas Hellström (VMware)
2019-11-14 13:17 Thomas Hellström (VMware)
2019-08-15  7:15 Thomas Hellström (VMware)
     [not found] <20190814073152.3120-1-thomas@shipmail.org>
2019-08-14 17:35 ` Thomas Hellström (VMware)
2019-06-19  7:25 Thomas Hellström (VMware)
2018-12-05 10:35 Thomas Hellstrom
2018-09-28 13:11 Thomas Hellstrom
2017-04-21 17:18 Sinclair Yeh
2017-03-31 23:32 Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter
2017-04-03 19:00   ` Sinclair Yeh
2017-01-30 19:46 Sinclair Yeh
2015-11-06 15:29 Thomas Hellstrom
2015-11-02  8:23 Thomas Hellstrom
2015-08-06 12:54 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=20170828202237.GA4229@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.