From: Sean Paul <seanpaul@chromium.org>
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] drm-misc-next-fixes
Date: Thu, 20 Apr 2017 16:11:48 -0400 [thread overview]
Message-ID: <20170420201148.sa3axehekrlsa2aj@art_vandelay> (raw)
Hi Dave,
A few fixes for you to pick up. The driver changes are trivial, and the
maintainer change was necessitated by the sti fix. The headliner here is the
dma_buf_ops rename, since it touches so many drivers. Everything looks sane and
builds with that change, so it shouldn't cause problems.
drm-misc-next-fixes-2017-04-20:
Core changes:
- Maintain sti via drm-misc (Vincent)
- Rename dma_buf_ops->kmap_* to avoid naming collision (Logan)
Driver changes:
- Fix UHD displays on stih407 (Vincent)
- Fix uninitialized var return in atmel-hlcdc (Dan)
Take care, Sean
The following changes since commit 8cb68c83ab99a474ae847602f0c514d0fe17cc82:
drm: Fix get_property logic fumble (2017-04-12 18:11:32 +0200)
are available in the git repository at:
git://anongit.freedesktop.org/git/drm-misc tags/drm-misc-next-fixes-2017-04-20
for you to fetch changes up to f9b67f0014cba18f1aabb6fa9272335a043eb6fd:
dma-buf: Rename dma-ops to prevent conflict with kunmap_atomic macro (2017-04-20 13:47:46 +0530)
----------------------------------------------------------------
drm-misc-next-fixes-2017-04-20
Core changes:
- Maintain sti via drm-misc (Vincent)
- Rename dma_buf_ops->kmap_* to avoid naming collision (Logan)
Driver changes:
- Fix UHD displays on stih407 (Vincent)
- Fix uninitialized var return in atmel-hlcdc (Dan)
----------------------------------------------------------------
Dan Carpenter (1):
drm: atmel-hlcdc: Uninitialized return in atmel_hlcdc_create_outputs()
Logan Gunthorpe (1):
dma-buf: Rename dma-ops to prevent conflict with kunmap_atomic macro
Vincent Abriou (2):
MAINTAINERS: add drm/sti driver into drm-misc
drm/sti: fix GDP size to support up to UHD resolution
MAINTAINERS | 2 +-
drivers/dma-buf/dma-buf.c | 16 ++++++++--------
drivers/gpu/drm/armada/armada_gem.c | 8 ++++----
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 5 ++---
drivers/gpu/drm/drm_prime.c | 8 ++++----
drivers/gpu/drm/i915/i915_gem_dmabuf.c | 8 ++++----
drivers/gpu/drm/i915/selftests/mock_dmabuf.c | 8 ++++----
drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c | 8 ++++----
drivers/gpu/drm/sti/sti_gdp.c | 12 +++++++-----
drivers/gpu/drm/tegra/gem.c | 8 ++++----
drivers/gpu/drm/udl/udl_dmabuf.c | 8 ++++----
drivers/gpu/drm/vmwgfx/vmwgfx_prime.c | 8 ++++----
drivers/media/v4l2-core/videobuf2-dma-contig.c | 4 ++--
drivers/media/v4l2-core/videobuf2-dma-sg.c | 4 ++--
drivers/media/v4l2-core/videobuf2-vmalloc.c | 4 ++--
drivers/staging/android/ion/ion.c | 8 ++++----
include/linux/dma-buf.h | 22 +++++++++++-----------
17 files changed, 71 insertions(+), 70 deletions(-)
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-04-20 20:11 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 20:11 Sean Paul [this message]
2017-04-20 21:50 ` [PULL] drm-misc-next-fixes Daniel Vetter
2017-04-21 15:29 ` Sumit Semwal
2017-04-21 18:10 ` Sean Paul
-- strict thread matches above, loose matches on Subject: below --
2026-06-11 20:50 Maarten Lankhorst
2026-06-05 7:57 Maarten Lankhorst
2026-04-23 13:08 Thomas Zimmermann
2026-04-17 6:14 Thomas Zimmermann
2026-04-09 11:39 Thomas Zimmermann
2026-02-05 11:22 Maxime Ripard
2026-01-29 8:58 Maxime Ripard
2025-12-10 10:21 Maarten Lankhorst
2025-11-26 15:20 Maarten Lankhorst
2025-10-02 12:23 Thomas Zimmermann
2025-09-25 6:42 Thomas Zimmermann
2025-09-18 6:45 Thomas Zimmermann
2025-08-12 6:47 Thomas Zimmermann
2025-07-24 6:52 Maxime Ripard
2025-06-05 17:02 Maarten Lankhorst
2025-04-04 6:51 Thomas Zimmermann
2025-03-27 14:18 Thomas Zimmermann
2025-03-13 18:01 Thomas Zimmermann
2025-01-24 15:25 Maarten Lankhorst
2025-01-24 16:09 ` Simona Vetter
2025-01-16 8:45 Maxime Ripard
2024-11-28 13:01 Maarten Lankhorst
2024-09-05 11:38 Thomas Zimmermann
2024-07-25 14:59 Maxime Ripard
2024-07-19 7:39 Maxime Ripard
2024-07-11 11:43 Maxime Ripard
2024-06-06 22:12 Maarten Lankhorst
2024-05-23 4:41 Maarten Lankhorst
2024-05-16 15:00 Maarten Lankhorst
2024-05-08 10:36 Maarten Lankhorst
2024-03-21 16:19 Thomas Zimmermann
2024-03-14 8:28 Thomas Zimmermann
2024-03-07 12:46 Thomas Zimmermann
2024-02-29 8:53 Thomas Zimmermann
2024-01-19 12:13 Maxime Ripard
2024-01-11 10:11 Maxime Ripard
2024-01-04 14:45 Maxime Ripard
2023-12-21 8:36 Maxime Ripard
2019-11-20 20:49 Sean Paul
2019-11-13 21:10 Sean Paul
2019-11-06 20:27 Sean Paul
2019-09-23 16:09 Maxime Ripard
2019-09-18 14:09 Maxime Ripard
2019-09-06 7:05 Maxime Ripard
2019-07-18 15:14 Sean Paul
2019-07-12 8:33 Maarten Lankhorst
2019-06-27 13:03 Maarten Lankhorst
2019-05-15 20:17 Sean Paul
2019-05-08 20:51 Sean Paul
2019-05-01 19:09 Sean Paul
2019-04-24 21:06 Sean Paul
2019-03-13 19:21 Maxime Ripard
2019-03-06 10:54 Maxime Ripard
2019-01-02 17:26 Maarten Lankhorst
2018-10-31 20:19 Sean Paul
2018-10-17 20:07 Sean Paul
2018-10-10 20:39 Sean Paul
2018-08-22 19:38 Sean Paul
2018-08-02 11:17 Gustavo Padovan
2018-06-15 8:11 Maarten Lankhorst
2018-05-31 8:11 Maarten Lankhorst
2018-04-11 14:03 Sean Paul
2018-04-04 19:14 Sean Paul
2018-03-28 19:13 Sean Paul
2018-01-31 15:09 Gustavo Padovan
2018-01-18 17:09 Gustavo Padovan
2017-11-23 19:45 Daniel Vetter
2017-11-08 13:00 Daniel Vetter
2017-11-07 13:44 Daniel Vetter
2017-08-28 21:22 Sean Paul
2017-07-10 19:58 Sean Paul
2017-06-27 20:53 Sean Paul
2017-04-12 22:58 Sean Paul
2017-02-27 15:52 Daniel Vetter
2017-02-15 13:54 Jani Nikula
2017-02-16 9:39 ` Jani Nikula
2017-02-09 8:43 Daniel Vetter
2016-12-10 21:52 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=20170420201148.sa3axehekrlsa2aj@art_vandelay \
--to=seanpaul@chromium.org \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox