From: Eric Anholt <eric@anholt.net>
To: Daniel Vetter <daniel@ffwll.ch>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: kernel@pengutronix.de, dri-devel@lists.freedesktop.org,
Cawa Cheng <cawa.cheng@mediatek.com>,
Jie Qiu <jie.qiu@mediatek.com>
Subject: Re: [GIT PULL] MT8173 DRM support
Date: Wed, 20 Apr 2016 09:21:17 -0700 [thread overview]
Message-ID: <87potks136.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20160420151957.GN2510@phenom.ffwll.local>
[-- Attachment #1.1: Type: text/plain, Size: 1570 bytes --]
Daniel Vetter <daniel@ffwll.ch> writes:
> On Wed, Apr 20, 2016 at 03:36:16PM +0200, Matthias Brugger wrote:
>>
>>
>> On 19/04/16 15:42, Philipp Zabel wrote:
>> >Hi Dave,
>> >
>> >please consider pulling this tag with initial MediaTek MT8173 DRM
>> >support, corresponding to v14 of the patch series. These patches have
>> >been mostly stable for the last few rounds. I'll follow up with the HDMI
>> >encoder support pending review of the latest version.
>> >
>>
>> Please don't pull
>> e34ba70de8c4 ("arm64: dts: mt8173: Add display subsystem related nodes")
>> If you pull the rest, this patch will go through my branch.
>
> So not on top of this at all, but do we have to split up arm drm drivers
> so much? Generally this stuff goes in through one tree with the driver,
> with acks from other subsystem as needed. That ack seems to be missing,
> but imo better to supply it and just get this pull req through. Or double
> merge a patch, we do that fairly often.
>
> Anyway just a comment, but sitting outside watching I think arm has a
> pretty serious problem with tree proliferation. And it's not helping to
> get fairly simple drivers like this one merged ...
DT changes do get merged through the arm DT tree separately. ARM has
absurd tree proliferation, but I think in this case it actually makes
sense. DT is the most common place I have merge conflicts when working
on platform enabling across the steaming piles of subsystem trees out
there, and keeping DT separate means that a merged -next tree can be
built sanely.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-20 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 13:42 [GIT PULL] MT8173 DRM support Philipp Zabel
2016-04-20 13:36 ` Matthias Brugger
2016-04-20 15:19 ` Daniel Vetter
2016-04-20 16:18 ` Matthias Brugger
2016-04-20 16:21 ` Eric Anholt [this message]
2016-04-20 17:32 ` Daniel Vetter
2016-04-20 17:42 ` Philipp Zabel
2016-04-21 19:50 ` Dave Airlie
2016-04-22 8:10 ` Philipp Zabel
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=87potks136.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=cawa.cheng@mediatek.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jie.qiu@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=matthias.bgg@gmail.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 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.