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: [git pull] vmwgfx-fixes-4.17
Date: Thu, 24 May 2018 12:42:22 +0200 [thread overview]
Message-ID: <20180524104222.13953-1-thellstrom@vmware.com> (raw)
Hi Dave,
Three fixes for vmwgfx. Two are cc'd stable and fix host logging and its
error paths on 32-bit VMs. One is a fix for a hibernate flaw
introduced with the 4.17 merge window.
The following changes since commit 91ba9f28a3de97761c2b5fd5df5d88421268e507:
drm/vmwgfx: Set dmabuf_size when vmw_dmabuf_init is successful (2018-05-16 08:01:20 +0200)
are available in the Git repository at:
git://people.freedesktop.org/~thomash/linux vmwgfx-fixes-4.17
for you to fetch changes up to 6a93cea15ed38e2dba4a0552483d28b7a87a03bd:
drm/vmwgfx: Schedule an fb dirty update after resume (2018-05-23 16:52:55 +0200)
----------------------------------------------------------------
Thomas Hellstrom (3):
drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
drm/vmwgfx: Fix host logging / guestinfo reading error paths
drm/vmwgfx: Schedule an fb dirty update after resume
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 5 ----
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 1 -
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 22 ++++++-----------
drivers/gpu/drm/vmwgfx/vmwgfx_msg.c | 48 ++++++++++++++++++++++++-------------
drivers/gpu/drm/vmwgfx/vmwgfx_msg.h | 25 ++++++++++++-------
5 files changed, 55 insertions(+), 46 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-05-24 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 10:42 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-16 19:37 [git pull] vmwgfx-fixes-4.17 Thomas Hellstrom
2018-05-03 8:08 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=20180524104222.13953-1-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