From: Sinclair Yeh <syeh@vmware.com>
To: airlied@redhat.com
Cc: thellstrom@vmware.com, dri-devel@lists.freedesktop.org
Subject: [git pull] vmwgfx-next
Date: Mon, 30 Jan 2017 11:46:08 -0800 [thread overview]
Message-ID: <20170130194607.GA43245@syeh-m01.local> (raw)
Hi Dave,
This is to address what we've discussed, moving some of the minor changes
into a drm-next request.
-----
The following changes since commit f0493e653f9679114d1dfd54ab88b54ce95576e1:
drm/mgag200: Added support for the new device G200eH3 (2017-01-23 11:57:08 +1000)
are available in the git repository at:
git://people.freedesktop.org/~syeh/repos_linux drm-vmwgfx-next
for you to fetch changes up to 5d25fde23b3176c7f94d2a992cb9762707d7c2a0:
drm/vmwgfx: Use kmemdup instead of kmalloc and memcpy (2017-01-26 21:26:17 -0800)
----------------------------------------------------------------
Shyam Saini (1):
drm/vmwgfx: Use kmemdup instead of kmalloc and memcpy
Sinclair Yeh (1):
drm/vmwgfx: Fix depth input into drm_mode_legacy_fb_format
Thomas Hellstrom (4):
drm/vmwgfx: Clear uninitialized fields of a parameter
drm/vmwgfx: Annotate ignored return values
drm/vmwgfx: Clear an uninitialized struct member
drm/vmwgfx: Fix a potential integer overflow
drivers/gpu/drm/vmwgfx/device_include/svga3d_surfacedefs.h | 2 ++
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 3 +--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 4 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_mob.c | 7 +++----
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 4 ++--
7 files changed, 12 insertions(+), 12 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-01-30 20:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 19:46 Sinclair Yeh [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-16 9:29 [git pull] vmwgfx-next Thomas Hellström (VMware)
2020-01-20 21:09 ` Dave Airlie
2020-01-20 21:42 ` Thomas Hellström (VMware)
2020-01-21 9:49 ` Thomas Hellström (VMware)
2019-11-14 13:17 Thomas Hellström (VMware)
2019-08-15 7:15 Thomas Hellström (VMware)
[not found] <20190814073152.3120-1-thomas@shipmail.org>
2019-08-14 17:35 ` Thomas Hellström (VMware)
2019-06-19 7:25 Thomas Hellström (VMware)
2018-12-05 10:35 Thomas Hellstrom
2018-09-28 13:11 Thomas Hellstrom
2017-08-28 20:22 [Git PULL] vmwgfx-next Sinclair Yeh
2017-08-28 20:35 ` Dave Airlie
2017-08-28 20:39 ` Sinclair Yeh
2017-04-21 17:18 [git pull] vmwgfx-next Sinclair Yeh
2017-03-31 23:32 Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter
2017-04-03 19:00 ` Sinclair Yeh
2015-11-06 15:29 Thomas Hellstrom
2015-11-02 8:23 Thomas Hellstrom
2015-08-06 12:54 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=20170130194607.GA43245@syeh-m01.local \
--to=syeh@vmware.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@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