From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org
Subject: Re: [PATCH RFC v2 0/6] drm/i2c: Move tda998x to a couple encoder/connector
Date: Fri, 21 Mar 2014 11:21:18 +0000 [thread overview]
Message-ID: <20140321112118.GH7528@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <cover.1395397665.git.moinejf@free.fr>
On Fri, Mar 21, 2014 at 11:27:45AM +0100, Jean-Francois Moine wrote:
> The 'slave encoder' structure of the tda998x driver asks for glue
> between the DRM driver and the encoder/connector structures.
Given how close we are to the coming merge window, that the discussion
about the of-graph bindings is still going on without concensus being
reached, and that this driver is not in staging, this needs to be
delayed until the following merge window when hopefully we have a
clearer picture about the DT side of this.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
prev parent reply other threads:[~2014-03-21 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 10:27 [PATCH RFC v2 0/6] drm/i2c: Move tda998x to a couple encoder/connector Jean-Francois Moine
2014-03-21 8:52 ` [PATCH RFC v2 6/6] ARM: AM33XX: dts: Change the tda998x description Jean-Francois Moine
2014-03-21 9:31 ` [PATCH RFC v2 3/6] drm/tilcd: dts: Add the video output port Jean-Francois Moine
2014-03-21 9:31 ` [PATCH RFC v2 5/6] drm/tilcd: dts: Remove unused slave description Jean-Francois Moine
2014-03-21 9:48 ` [PATCH RFC v2 1/6] drm/i2c: tda998x: Add the required port property Jean-Francois Moine
2014-03-21 11:21 ` Russell King - ARM Linux [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=20140321112118.GH7528@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
/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).