From: Thomas Hellstrom <thellstrom@vmware.com>
To: arlied@redhat.com, airlied@gmail.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: [PULL] vmwgfx-fixes-3.18
Date: Fri, 31 Oct 2014 11:05:01 +0100 [thread overview]
Message-ID: <1414749901-3176-1-git-send-email-thellstrom@vmware.com> (raw)
Hi, Dave
A critical 3.18 regression fix from Rob, (thanks!)
A fix to avoid advertizing modes we can't support from Sinclair
(welcome Sinclair!)
and a fix for an incorrect hash key computation from me that is
completely harmless, but can wait 'til the next merge window if necessary.
(I can't really bother stable with this one).
The following changes since commit d34d4d8af8d24afe4e16128e4e7f5c5967c89027:
Merge branch 'drm-fixes-3.18' of git://people.freedesktop.org/~agd5f/linux into drm-fixes (2014-10-31 06:54:51 +1000)
are available in the git repository at:
git://people.freedesktop.org/~thomash/linux vmwgfx-fixes-3.18
for you to fetch changes up to 9a72384d86b26cb8a2b25106677e1197f606668f:
drm/vmwgfx: Filter out modes those cannot be supported by the current VRAM size. (2014-10-31 09:58:06 +0100)
----------------------------------------------------------------
Rob Clark (1):
drm/vmwgfx: fix lock breakage
Sinclair Yeh (1):
drm/vmwgfx: Filter out modes those cannot be supported by the current VRAM size.
Thomas Hellstrom (1):
drm/vmwgfx: Fix hash key computation
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf_res.c | 3 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 6 +++++-
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 24 +++++++++++++++++-------
3 files changed, 24 insertions(+), 9 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2014-10-31 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1414749901-3176-1-git-send-email-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=arlied@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