All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: DSS DT changes
Date: Fri, 21 Mar 2014 12:52:38 +0200	[thread overview]
Message-ID: <532C19F6.6060703@ti.com> (raw)
In-Reply-To: <20140319153046.GA12934@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

On 19/03/14 17:30, Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [140319 04:29]:
>> Hi Tony,
>>
>> Is it too late to get the DSS dts changes via arm tree?
> 
> Yes too late..
>  
>> I now got everything working fine so that the dts changes and the
>> omapdss driver changes can be merged independently. It would be cleaner
>> if dts changes can go through the proper channel.
>>
>> If you can still take them, I've attached the patches, based on your
>> omap-for-v3.15/dt branch.
>>
>> I also attached the bindings docs. Those I can take via my tree, but I'm
>> not sure if they are supposed to go with the dts changes or with the
>> driver changes, so I have them here also.
>>
>> And I've pushed the changes to my tree:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git
>>
>> The branches are:
>>
>> 3.15/dss-dt-dts - contains the .dts changes
>> 3.15/dss-dt - contains the driver changes + binding docs
> 
> These look OK to me and would be good to get in so we can move
> on with dropping more legacy platform data.
> 
> As you have my acks there, so please feel free to send
> your 3.15/dss-dt-dts along with the DSS patches after the
> arm-soc branches have been merged.

Ok. All this is now in linux-next.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-03-21 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 11:25 DSS DT changes Tomi Valkeinen
2014-03-19 15:30 ` Tony Lindgren
2014-03-21 10:52   ` Tomi Valkeinen [this message]
2014-03-28  2:47     ` Sebastian Reichel

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=532C19F6.6060703@ti.com \
    --to=tomi.valkeinen@ti.com \
    --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.