dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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.20
Date: Thu, 13 Dec 2018 13:28:15 +0100	[thread overview]
Message-ID: <20181213122815.10581-1-thellstrom@vmware.com> (raw)

Hi Dave,

One redundant return statement fix, and one DOS fix for a regression introduced
with 4.20.

The following changes since commit 73b6f96cbc0162787bcbdac5f538167084c8d605:

  Merge branch 'drm-fixes-4.20' of git://people.freedesktop.org/~agd5f/linux into drm-fixes (2018-11-11 04:23:02 +1000)

are available in the Git repository at:

  git://people.freedesktop.org/~thomash/linux vmwgfx-fixes-4.20

for you to fetch changes up to fd567467753fac9f9f477550065018e7f4e3c8f3:

  drm/vmwgfx: Protect from excessive execbuf kernel memory allocations v3 (2018-12-13 13:04:25 +0100)

----------------------------------------------------------------
Colin Ian King (1):
      drm/vmwgfx: remove redundant return ret statement

Thomas Hellstrom (1):
      drm/vmwgfx: Protect from excessive execbuf kernel memory allocations v3

 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c        |  4 +++-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h        |  5 ++++
 drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c    |  4 ++--
 drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c   | 36 +++++++++++++++++++++++++++++
 drivers/gpu/drm/vmwgfx/vmwgfx_validation.c | 21 ++++++++++++++++-
 drivers/gpu/drm/vmwgfx/vmwgfx_validation.h | 37 ++++++++++++++++++++++++++++++
 6 files changed, 103 insertions(+), 4 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2018-12-13 12:28 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=20181213122815.10581-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