From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] AM43xx & OMAP5 DSS DT changes
Date: Wed, 21 May 2014 08:02:31 -0700 [thread overview]
Message-ID: <20140521150231.GH17417@atomide.com> (raw)
In-Reply-To: <1400676625-30078-1-git-send-email-tomi.valkeinen@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [140521 05:51]:
> Hi,
>
> Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock
> related changes separately, and I removed OMAP5's RFBI node, which depends on
> more clock changes. The RFBI driver doesn't work at the moment anyway, so
> removing the RFBI node should not be an issue.
>
> Tony, if these look fine (the rfbi change is the only one compared to the
> previous versions), can you queue them for 3.16?
Probably best that you do a late branch again after arm-soc dts changes
have been merged. Sounds like you have at least that macro dependency
to omap-for-v3.16/dt-v2 so you should probably base your branch on
that. So for this:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2014-05-21 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 12:50 [PATCH 0/6] AM43xx & OMAP5 DSS DT changes Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 1/6] ARM: dts: am4372.dtsi: add DSS information Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 2/6] ARM: dts: am437x-gp-evm: add LCD data Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 3/6] ARM: dts: am43x-epos-evm: " Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 4/6] ARM: dts: omap5.dtsi: add DSS nodes Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 5/6] ARM: dts: omap5-uevm.dts: add tca6424a Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 6/6] ARM: dts: omap5-uevm.dts: add display nodes Tomi Valkeinen
2014-05-21 15:02 ` Tony Lindgren [this message]
2014-05-21 15:17 ` [PATCH 0/6] AM43xx & OMAP5 DSS DT changes Tomi Valkeinen
2014-05-21 15:26 ` Tony Lindgren
2014-05-21 15:31 ` Tomi Valkeinen
2014-05-21 15:41 ` Tony Lindgren
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=20140521150231.GH17417@atomide.com \
--to=tony@atomide.com \
--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).