From: Philipp Zabel <pza@pengutronix.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: kernel@pengutronix.de, dri-devel@lists.freedesktop.org,
Russell King <rmk+kernel@arm.linux.org.uk>,
Grant Likely <grant.likely@linaro.org>,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v4 0/3] drm_of_encoder_active_endpoint helpers
Date: Sat, 30 Jan 2016 16:04:27 +0100 [thread overview]
Message-ID: <20160130150427.GA29468@pengutronix.de> (raw)
In-Reply-To: <13720416.3qJ6rahZv9@phil>
On Sat, Jan 30, 2016 at 03:38:09PM +0100, Heiko Stuebner wrote:
> Hi Philipp,
>
> Am Freitag, 29. Januar 2016, 10:58:57 schrieb Philipp Zabel:
> > I'm just looking for feedback whether
> > I should include the rockchip patch in the next imx-drm pull request.
>
> I'm hoping that we'd get the analogix dp driver sorted for 4.6 as well,
> which having that change in the imx-tree would make quite difficult.
>
> One possible solution may be to put patch1 into an immutable branch, that
> you can then merge into your imx-tree and Mark can merge into the Rockchip
> drm-tree?
Can do, I'll put them onto a separate branch.
best regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-01-30 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 9:58 [PATCH v4 0/3] drm_of_encoder_active_endpoint helpers Philipp Zabel
2016-01-29 9:58 ` [PATCH v4 1/3] drm: add " Philipp Zabel
2016-01-29 9:58 ` [PATCH v4 2/3] drm/imx: remove imx_drm_encoder_get_mux_id Philipp Zabel
2016-01-29 9:59 ` [PATCH v4 3/3] drm/rockchip: remove rockchip_drm_encoder_get_mux_id Philipp Zabel
2016-01-30 14:38 ` [PATCH v4 0/3] drm_of_encoder_active_endpoint helpers Heiko Stuebner
2016-01-30 15:04 ` Philipp Zabel [this message]
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=20160130150427.GA29468@pengutronix.de \
--to=pza@pengutronix.de \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=rmk+kernel@arm.linux.org.uk \
/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