From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] drm/rockchip: Don't build rockchip_drm_vop as modules
Date: Mon, 25 Jan 2016 12:09:31 +0100 [thread overview]
Message-ID: <4712230.210ZLu46G4@diego> (raw)
In-Reply-To: <1453719247.30130.22.camel@collabora.co.uk>
Am Montag, 25. Januar 2016, 11:54:07 schrieb Sjoerd Simons:
> On Wed, 2016-01-13 at 16:22 +0800, Mark Yao wrote:
> > rockchip_drm_vop's module init had moved to rockchip_vop_reg.c
> > so no need to build rockchip_drm_vop.ko
>
> Looks like this didn't make it for the Linux 4.5 merge window, which
> unfortunately means in 4.5-rc1 DRM on rockchip is broken :/
but it is in the fixes pull request Mark sent to Dave on friday
next prev parent reply other threads:[~2016-01-25 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 8:22 [PATCH 0/2] drm/rockchip: cleanup unnecessary modules and symbol Mark Yao
2016-01-13 8:22 ` [PATCH 1/2] drm/rockchip: Don't build rockchip_drm_vop as modules Mark Yao
2016-01-25 10:54 ` Sjoerd Simons
2016-01-25 11:09 ` Heiko Stübner [this message]
2016-01-13 8:22 ` [PATCH 2/2] drm/rockchip: cleanup unnecessary export symbol Mark Yao
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=4712230.210ZLu46G4@diego \
--to=heiko@sntech.de \
--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;
as well as URLs for NNTP newsgroup(s).