From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@redhat.com, airlied@gmail.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: Wed, 3 Dec 2014 01:01:19 -0800 [thread overview]
Message-ID: <1417597279-4321-1-git-send-email-thellstrom@vmware.com> (raw)
Dave,
A number of bug fixes.
The following changes since commit 4fcd01d0f34645710ac92d5523e26019428b0806:
drm: rcar-du: Fix NULL encoder pointer dereference (2014-12-03 08:28:48 +1000)
are available in the git repository at:
git://people.freedesktop.org/~thomash/linux
for you to fetch changes up to b8ccd1e490de8d9b9a968f859c003a10882ad8c8:
drm/vmwgfx: (Re)bind shaders to MOBs with the correct offset (2014-12-03 00:48:14 -0800)
----------------------------------------------------------------
Thomas Hellstrom (4):
drm/vmwgfx: Fix error printout on signals pending
drm/vmwgfx: Don't use memory accounting for kernel-side fence objects
drm/vmwgfx: Fix fence event code
drm/vmwgfx: (Re)bind shaders to MOBs with the correct offset
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 8 +++++--
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 39 +++++++---------------------------
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 2 +-
3 files changed, 15 insertions(+), 34 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-12-03 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 9:01 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-11 19:02 [PULL] vmwgfx-next Thomas Hellstrom
2015-04-01 19:33 ` Thomas Hellstrom
2014-07-04 10:44 Thomas Hellstrom
2014-04-04 6:19 Thomas Hellstrom
2014-03-28 13:35 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=1417597279-4321-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