dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
To: airlied@gmail.com, daniel@ffwll.ch, dri-devel@lists.freedesktop.org
Cc: pv-drivers@vmware.com,
	"Thomas Hellström" <thomas_os@shipmail.org>,
	linux-graphics-maintainer@vmware.com
Subject: [git pull] vmwgfx-fixes-5.3
Date: Thu,  5 Sep 2019 15:00:55 +0200	[thread overview]
Message-ID: <20190905130055.2647-1-thomas_os@shipmail.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]

From: Thomas Hellström <thomas_os@shipmail.org>

Dave, Daniel

A single fix from Dan for a previous fix that generated a regression.

The following changes since commit 6b7c3b86f0b63134b2ab56508921a0853ffa687a:

  drm/vmwgfx: fix memory leak when too many retries have occurred (2019-08-08 11:22:54 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 08b0c891605acf727e43e3e03a25857d3e789b61:

  drm/vmwgfx: Fix double free in vmw_recv_msg() (2019-09-05 14:44:28 +0200)

----------------------------------------------------------------
Dan Carpenter (1):
      drm/vmwgfx: Fix double free in vmw_recv_msg()

 drivers/gpu/drm/vmwgfx/vmwgfx_msg.c | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-09-05 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 13:00 Thomas Hellström (VMware) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-08  9:46 [git pull] vmwgfx-fixes-5.3 Thomas Hellström (VMware)

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=20190905130055.2647-1-thomas_os@shipmail.org \
    --to=thomas_os@shipmail.org \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --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