From: Thomas Hellstrom <thellstrom@vmware.com>
To: "airlied@redhat.com" <airlied@redhat.com>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Cc: Pv-drivers <Pv-drivers@vmware.com>,
Thomas Hellstrom <thellstrom@vmware.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: [git pull] vmwgfx-fixes-5.1
Date: Thu, 21 Mar 2019 11:21:09 +0000 [thread overview]
Message-ID: <20190321112026.114328-1-thellstrom@vmware.com> (raw)
Dave and Daniel,
Two fixes CC'd stable. One fix for a long-standing a bit hard-to-trigger fbdev
modesetting bug and one out-of-bo-id fix.
The following changes since commit 1c163f4c7b3f621efff9b28a47abb36f7378d783:
Linux 5.0 (2019-03-03 15:21:29 -0800)
are available in the Git repository at:
git://people.freedesktop.org/~thomash/linux vmwgfx-fixes-5.1
for you to fetch changes up to c2d311553855395764e2e5bf401d987ba65c2056:
drm/vmwgfx: Don't double-free the mode stored in par->set_mode (2019-03-20 07:57:01 +0100)
----------------------------------------------------------------
Deepak Rawat (1):
drm/vmwgfx: Return 0 when gmrid::get_node runs out of ID's
Thomas Zimmermann (1):
drm/vmwgfx: Don't double-free the mode stored in par->set_mode
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 12 +++---------
drivers/gpu/drm/vmwgfx/vmwgfx_gmrid_manager.c | 2 +-
2 files changed, 4 insertions(+), 10 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-21 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 11:21 Thomas Hellstrom [this message]
2019-04-25 7:51 [git pull] vmwgfx-fixes-5.1 Thomas Hellstrom
2019-04-25 20:41 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=20190321112026.114328-1-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=Pv-drivers@vmware.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.