From: "Thomas Hellström (VMware)" <thomas@shipmail.org>
To: airlied@gmail.com, daniel@ffwll.ch, dri-devel@lists.freedesktop.org
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thomas@shipmail.org>,
linux-graphics-maintainer@vmware.com
Subject: [git pull] vmwgfx-next
Date: Thu, 15 Aug 2019 09:15:58 +0200 [thread overview]
Message-ID: <20190815071558.37481-1-thomas@shipmail.org> (raw)
From: Thomas Hellstrom (VMware) <thomas@shipmail.org>
Dave, Daniel
A couple of independent patches extracted from the 5.3 pull request, fixed for
merge conflicts and a single unused variable warning.
And the drmP.h removal from Sam.
/Thomas
The following changes since commit e7f7287bf5f746d29f3607178851246a005dd398:
Merge tag 'drm-next-5.4-2019-08-09' of git://people.freedesktop.org/~agd5f/linux into drm-next (2019-08-12 14:20:21 +1000)
are available in the Git repository at:
git://people.freedesktop.org/~thomash/linux/ vmwgfx-next
for you to fetch changes up to a0a63940b0c9ebc6d3156bbfe0c2cf7560b580cd:
drm/vmwgfx: Assign eviction priorities to resources (2019-08-15 08:40:05 +0200)
----------------------------------------------------------------
Deepak Rawat (2):
drm/vmwgfx: Add debug message for layout change ioctl
drm/vmwgfx: Use VMW_DEBUG_KMS for vmwgfx mode-setting user errors
Sam Ravnborg (2):
drm/vmwgfx: drop use of drmP.h in header files
drm/vmwgfx: drop reminaing users of drmP.h
Thomas Hellstrom (2):
drm/vmwgfx: Kill unneeded legacy security features
drm/vmwgfx: Assign eviction priorities to resources
drivers/gpu/drm/vmwgfx/ttm_lock.c | 100 --------------
drivers/gpu/drm/vmwgfx/ttm_lock.h | 32 +----
drivers/gpu/drm/vmwgfx/ttm_object.h | 7 +-
drivers/gpu/drm/vmwgfx/vmwgfx_binding.h | 3 +-
drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 3 +-
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 3 +
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 4 +
drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c | 13 +-
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 180 ++------------------------
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 126 ++++++++++++++----
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 8 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 3 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fence.h | 5 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 6 +-
drivers/gpu/drm/vmwgfx/vmwgfx_gmr.c | 4 +-
drivers/gpu/drm/vmwgfx/vmwgfx_irq.c | 3 +-
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 33 +++--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 6 +-
drivers/gpu/drm/vmwgfx/vmwgfx_mob.c | 2 +
drivers/gpu/drm/vmwgfx/vmwgfx_msg.c | 11 +-
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | 6 +-
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 60 ++++++---
drivers/gpu/drm/vmwgfx/vmwgfx_resource_priv.h | 2 +
drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 6 +-
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 8 +-
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 9 +-
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 10 +-
drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c | 1 -
drivers/gpu/drm/vmwgfx/vmwgfx_validation.h | 3 +-
30 files changed, 264 insertions(+), 395 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-08-15 7:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:15 Thomas Hellström (VMware) [this message]
-- 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)
[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-08-28 20:22 [Git PULL] vmwgfx-next Sinclair Yeh
2017-08-28 20:35 ` Dave Airlie
2017-08-28 20:39 ` Sinclair Yeh
2017-04-21 17:18 [git pull] vmwgfx-next 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=20190815071558.37481-1-thomas@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--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