From: daniel@ffwll.ch (Daniel Vetter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] drm: fixes for merge-window regressions
Date: Wed, 18 May 2016 18:05:24 +0200 [thread overview]
Message-ID: <20160518160524.GI27098@phenom.ffwll.local> (raw)
In-Reply-To: <1463579106-400827-1-git-send-email-arnd@arndb.de>
On Wed, May 18, 2016 at 03:45:01PM +0200, Arnd Bergmann wrote:
> A couple of new warnings and build errors appeared through the DRM
> tree in linux-next after the merge window opened. The first patch
> here is for scripts/headers_check.pl, but as the bug is only
> present in drm-next at the moment, it would be good to add all
> five patches to that tree before they make it into mainline.
>
> It's likely that some of these have already been fixed since
> this morning's linux-next, so just ignore the ones are no
> longer needed.
>
> Arnd Bergmann (5):
> headers_check: don't warn about c++ guards
> drm: mediatek: add CONFIG_OF dependency
> drm: mediatek: fixup drm_gem_object_lookup API change
> drm: exynos: mark pm functions as __maybe_unused
> drm: remove unused dev variables
None of the actual patches seems to have made it onto dri-devel. Stuck
somewhere?
-Daniel
>
> drivers/gpu/drm/armada/armada_crtc.c | 1 -
> drivers/gpu/drm/exynos/exynos_hdmi.c | 6 ++----
> drivers/gpu/drm/mediatek/Kconfig | 1 +
> drivers/gpu/drm/mediatek/mtk_drm_fb.c | 2 +-
> drivers/gpu/drm/mediatek/mtk_drm_gem.c | 2 +-
> drivers/gpu/drm/nouveau/nouveau_gem.c | 1 -
> drivers/gpu/drm/nouveau/nv50_display.c | 1 -
> drivers/gpu/drm/radeon/radeon_cs.c | 1 -
> scripts/headers_check.pl | 4 ++++
> 9 files changed, 9 insertions(+), 10 deletions(-)
>
>
> Cc: Russell King <rmk+kernel@armlinux.org.uk>
> Cc: Inki Dae <inki.dae@samsung.com>
> Cc: Joonyoung Shim <jy0922.shim@samsung.com>
> Cc: Seung-Woo Kim <sw0312.kim@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> Cc: Kukjin Kim <kgene@kernel.org>
> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Cc: Matthias Brugger <matthias.bgg@gmail.com>
> Cc: Ben Skeggs <bskeggs@redhat.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: "Christian K?nig" <christian.koenig@amd.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: dri-devel at lists.freedesktop.org
> Cc: linux-kernel at vger.kernel.org
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: linux-samsung-soc at vger.kernel.org
> Cc: linux-mediatek at lists.infradead.org
> Cc: nouveau at lists.freedesktop.org
>
> --
> 2.7.0
>
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-05-18 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 13:45 [PATCH 0/5] drm: fixes for merge-window regressions Arnd Bergmann
2016-05-18 16:05 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-18 16:07 Arnd Bergmann
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=20160518160524.GI27098@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=linux-arm-kernel@lists.infradead.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