From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, airlied@redhat.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: Fri, 4 Jul 2014 12:44:46 +0200 [thread overview]
Message-ID: <1404470686-3358-1-git-send-email-thellstrom@vmware.com> (raw)
Dave, A compat shader namespace fix that at the same tame makes much of the
code more generic in preparation for future use.
The following changes since commit bc1dfff04a5d4064ba0db1fab13f84ab4f333d2b:
Merge branch 'drm-nouveau-next' of git://anongit.freedesktop.org/git/nouveau/linux-2.6 into drm-next (2014-06-11 16:28:10 +1000)
are available in the git repository at:
git://people.freedesktop.org/~thomash/linux tags/vmwgfx-next-2014-07-04
for you to fetch changes up to 18e4a4669c5023eb1157f2a3f1bf6ca2b8535572:
drm/vmwgfx: Fix compat shader namespace (2014-07-04 12:12:09 +0200)
----------------------------------------------------------------
Pull request of 2014-07-04
----------------------------------------------------------------
Thomas Hellstrom (1):
drm/vmwgfx: Fix compat shader namespace
drivers/gpu/drm/vmwgfx/Makefile | 3 +-
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf_res.c | 341 +++++++++++++++++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 38 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 7 -
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 74 ++++--
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 227 +++++++++--------
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 396 +++++++++--------------------
7 files changed, 673 insertions(+), 413 deletions(-)
create mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf_res.c
next reply other threads:[~2014-07-04 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 10:44 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-12-03 9:01 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=1404470686-3358-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