dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: "airlied@gmail.com" <airlied@gmail.com>,
	"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, 25 Apr 2019 07:51:38 +0000	[thread overview]
Message-ID: <20190425075040.2829-1-thellstrom@vmware.com> (raw)

Dave, Daniel

A single fix for a layer violation requested by Cristoph.

The following changes since commit c2d311553855395764e2e5bf401d987ba65c2056:

  drm/vmwgfx: Don't double-free the mode stored in par->set_mode (2019-03-20 07:57:01 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 81103355b1e23345dbcdeccad59962a424da4a34:

  drm/vmwgfx: Fix dma API layer violation (2019-04-25 09:05:03 +0200)

----------------------------------------------------------------
Thomas Hellstrom (1):
      drm/vmwgfx: Fix dma API layer violation

 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 33 +++++----------------------------
 1 file changed, 5 insertions(+), 28 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-04-25  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25  7:51 Thomas Hellstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-25 20:41 [git pull] vmwgfx-fixes-5.1 Thomas Hellstrom
2019-03-21 11:21 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=20190425075040.2829-1-thellstrom@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=Linux-graphics-maintainer@vmware.com \
    --cc=Pv-drivers@vmware.com \
    --cc=airlied@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox