From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PULL] topic/drm-misc
Date: Thu, 28 Jul 2016 14:30:08 +0200 [thread overview]
Message-ID: <20160728123008.GA18178@phenom.ffwll.local> (raw)
Hi Dave,
A few more simple fixes that Sean&I collected. There's a bunch of bigger
things on dri-devel, but I think those are all too late for 4.8 really.
I'll try and go collect them after -rc1 for 4.9.
Cheers, Daniel
The following changes since commit e8d3ef02787fc72996cfb423180dc79764c239fa:
GPU-DRM-Exynos: Delete an unnecessary check before the function call "vunmap" (2016-07-21 14:06:33 -0400)
are available in the git repository at:
git://anongit.freedesktop.org/drm-intel tags/topic/drm-misc-2016-07-28
for you to fetch changes up to 12ae57aab43880eac500c43590e26d9d4411961b:
drm/arm: mali-dp: Fix error return code in malidp_bind() (2016-07-28 12:59:56 +0200)
----------------------------------------------------------------
Brian Starkey (1):
drm/arm: mali-dp: Set crtc.port to the port instead of the endpoint
Lee Jones (1):
drm/sti: use new Reset API
Lukas Wunner (1):
apple-gmux: Sphinxify docs
Markus Elfring (8):
GPU-DRM-OMAP: Delete unnecessary checks before two function calls
GPU-DRM-GMA500: Delete unnecessary checks before two function calls
drm/bridge: ps8622: Delete an unnecessary check before backlight_device_unregister()
drm/mgag200: Delete an unnecessary check before drm_gem_object_unreference_unlocked()
drm/qxl: Delete an unnecessary check before drm_gem_object_unreference_unlocked()
drm/vmwgfx: Delete an unnecessary check before the function call "vfree"
drm/etnaviv: Delete unnecessary checks before two function calls
drm/etnaviv: Optimize error handling in etnaviv_gem_new_userptr()
Stefan Christ (1):
drm/gma500: remove unnecessary stub for fb_ioctl()
Wei Yongjun (2):
drm/arm: mali-dp: Remove redundant dev_err call in malidp_bind()
drm/arm: mali-dp: Fix error return code in malidp_bind()
drivers/gpu/drm/arm/malidp_drv.c | 19 ++++++---
drivers/gpu/drm/bridge/parade-ps8622.c | 4 +-
drivers/gpu/drm/etnaviv/etnaviv_gem.c | 16 +++----
drivers/gpu/drm/gma500/cdv_intel_hdmi.c | 3 +-
drivers/gpu/drm/gma500/cdv_intel_lvds.c | 9 ++--
drivers/gpu/drm/gma500/framebuffer.c | 9 ----
drivers/gpu/drm/gma500/psb_drv.c | 6 +--
drivers/gpu/drm/gma500/psb_intel_lvds.c | 9 ++--
drivers/gpu/drm/mgag200/mgag200_main.c | 4 +-
drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c | 3 +-
drivers/gpu/drm/omapdrm/omap_fb.c | 4 +-
drivers/gpu/drm/qxl/qxl_display.c | 3 +-
drivers/gpu/drm/sti/sti_compositor.c | 4 +-
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 4 +-
drivers/platform/x86/apple-gmux.c | 55 +++++++++++++------------
15 files changed, 66 insertions(+), 86 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-07-28 12:30 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 12:30 Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-10 7:16 [PULL] topic/drm-misc Daniel Vetter
2016-10-27 18:53 Daniel Vetter
2016-10-24 7:21 Daniel Vetter
2016-10-13 8:28 Daniel Vetter
2016-10-11 8:03 Daniel Vetter
2016-10-05 9:29 Daniel Vetter
2016-10-03 13:39 Daniel Vetter
2016-10-04 2:48 ` Dave Airlie
2016-09-25 21:26 Daniel Vetter
2016-09-19 7:11 Daniel Vetter
2016-09-08 9:30 Jani Nikula
2016-08-31 16:48 Daniel Vetter
2016-08-23 19:53 Daniel Vetter
2016-08-12 17:18 Daniel Vetter
2016-07-22 8:10 Daniel Vetter
2016-07-14 8:32 Daniel Vetter
2016-07-11 5:55 Daniel Vetter
2016-06-22 9:21 Daniel Vetter
2016-06-22 11:13 ` Daniel Vetter
2016-06-22 11:22 ` Daniel Vetter
2016-06-14 21:48 Daniel Vetter
2016-06-15 15:16 ` Daniel Vetter
2016-06-15 15:40 ` Daniel Vetter
2016-06-07 20:00 Daniel Vetter
2016-06-01 7:29 Daniel Vetter
2016-05-18 19:53 Daniel Vetter
2016-05-17 16:49 Daniel Vetter
2016-05-12 22:28 Daniel Vetter
2016-05-08 16:35 Daniel Vetter
2016-05-04 21:25 Daniel Vetter
2016-04-29 8:13 Daniel Vetter
2016-04-21 9:31 Daniel Vetter
2016-04-01 13:11 Daniel Vetter
2016-03-22 14:48 Daniel Vetter
2016-03-09 9:56 Daniel Vetter
2016-03-14 6:47 ` Daniel Vetter
2016-02-18 19:51 Daniel Vetter
2016-02-12 13:21 Daniel Vetter
2016-02-08 10:36 Daniel Vetter
2016-01-17 16:07 Daniel Vetter
2015-12-23 12:43 Daniel Vetter
2015-12-18 16:39 Daniel Vetter
2015-12-14 9:26 Daniel Vetter
2015-12-04 10:46 Daniel Vetter
2015-11-26 8:17 Daniel Vetter
2015-10-22 19:42 Daniel Vetter
2015-10-19 13:21 Daniel Vetter
2015-10-08 7:37 Daniel Vetter
2015-09-25 12:18 Daniel Vetter
2015-09-22 9:05 Daniel Vetter
2015-09-22 9:17 ` Daniel Vetter
2015-09-14 15:22 Daniel Vetter
2015-09-16 14:45 ` Daniel Vetter
2015-09-21 21:40 ` Dave Airlie
2015-08-13 7:59 Daniel Vetter
2015-07-28 9:03 Daniel Vetter
2015-07-23 7:27 Daniel Vetter
2015-07-13 7:22 Daniel Vetter
2015-06-22 11:50 Daniel Vetter
2015-05-28 6:40 Daniel Vetter
2015-05-19 14:23 Daniel Vetter
2015-05-06 8:24 Daniel Vetter
2015-04-15 12:06 Daniel Vetter
2015-03-31 14:29 Daniel Vetter
2015-03-31 14:31 ` Daniel Vetter
2015-03-18 10:15 Daniel Vetter
2015-03-10 9:21 Daniel Vetter
2015-02-06 7:29 Daniel Vetter
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=20160728123008.GA18178@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.