From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] AM43xx & OMAP5 DSS DT changes
Date: Wed, 21 May 2014 18:17:10 +0300 [thread overview]
Message-ID: <537CC376.5050501@ti.com> (raw)
In-Reply-To: <20140521150231.GH17417@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On 21/05/14 18:02, Tony Lindgren wrote:
> * 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
There are no dependencies that I know of. Which macro dependency is that?
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] AM43xx & OMAP5 DSS DT changes
Date: Wed, 21 May 2014 18:17:10 +0300 [thread overview]
Message-ID: <537CC376.5050501@ti.com> (raw)
In-Reply-To: <20140521150231.GH17417@atomide.com>
On 21/05/14 18:02, Tony Lindgren wrote:
> * 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
There are no dependencies that I know of. Which macro dependency is that?
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140521/6b68bd54/attachment-0001.sig>
next prev parent reply other threads:[~2014-05-21 15:17 UTC|newest]
Thread overview: 24+ 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 ` Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 1/6] ARM: dts: am4372.dtsi: add DSS information Tomi Valkeinen
2014-05-21 12:50 ` 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 ` Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 3/6] ARM: dts: am43x-epos-evm: " Tomi Valkeinen
2014-05-21 12:50 ` Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 4/6] ARM: dts: omap5.dtsi: add DSS nodes Tomi Valkeinen
2014-05-21 12:50 ` Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 5/6] ARM: dts: omap5-uevm.dts: add tca6424a Tomi Valkeinen
2014-05-21 12:50 ` Tomi Valkeinen
2014-05-21 12:50 ` [PATCH 6/6] ARM: dts: omap5-uevm.dts: add display nodes Tomi Valkeinen
2014-05-21 12:50 ` Tomi Valkeinen
2014-05-21 15:02 ` [PATCH 0/6] AM43xx & OMAP5 DSS DT changes Tony Lindgren
2014-05-21 15:02 ` Tony Lindgren
2014-05-21 15:17 ` Tomi Valkeinen [this message]
2014-05-21 15:17 ` Tomi Valkeinen
2014-05-21 15:26 ` Tony Lindgren
2014-05-21 15:26 ` Tony Lindgren
2014-05-21 15:31 ` Tomi Valkeinen
2014-05-21 15:31 ` Tomi Valkeinen
2014-05-21 15:41 ` Tony Lindgren
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=537CC376.5050501@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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.