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, 3 May 2018 10:08:17 +0200 [thread overview]
Message-ID: <20180503080817.3819-1-thellstrom@vmware.com> (raw)
Hi, Dave,
Two fixes for now, one for a long standing problem uncovered by a commit
in the 4.17 merge window, one for a regression introduced by a previous
bugfix, Cc'd stable.
The following changes since commit bb1278e891662616ccf4584523318d5f7ddb3a7c:
Merge tag 'drm-misc-fixes-2018-04-25' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2018-04-26 11:09:56 +1000)
are available in the Git repository at:
git://people.freedesktop.org/~thomash/linux vmwgfx-fixes-4.17
for you to fetch changes up to 13f149d47392782baafd96d54d4e65f3b5ca342f:
drm/vmwgfx: Fix a buffer object leak (2018-04-26 09:59:30 +0200)
----------------------------------------------------------------
Thomas Hellstrom (2):
drm/vmwgfx: Clean up fbdev modeset locking
drm/vmwgfx: Fix a buffer object leak
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 31 ++++++++++---------------------
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 14 +++++++++++---
2 files changed, 21 insertions(+), 24 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-05-03 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 8:08 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-24 10:42 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=20180503080817.3819-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