linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 5/7] arm: add basic support for Mediatek MT6589 boards
Date: Mon, 21 Jul 2014 15:14:16 +0200	[thread overview]
Message-ID: <53CD1228.4050401@linaro.org> (raw)
In-Reply-To: <53C96DC7.10203@linaro.org>

On 07/18/2014 08:56 PM, Daniel Lezcano wrote:
> On 07/18/2014 12:47 PM, Heiko St?bner wrote:
>> Hi Daniel,
>>
>> Am Freitag, 18. Juli 2014, 11:46:51 schrieb Daniel Lezcano:
>>> On 07/07/2014 05:13 PM, Matthias Brugger wrote:
>>>> This adds a generic devicetree board file and a dtsi for boards
>>>> based on MT6589 SoCs from Mediatek.
>>>>
>>>> Apart from the generic parts (gic, clocks) the only component
>>>> currently supported are the timers.
>>>>
>>>> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>>>> --
>>>
>>> I will take this patchset through my tree but this patch touches an area
>>> I am not handling.
>>>
>>> Olof, Arnd, do you mind to ack this patch ?
>>
>> wouldn't it be easier to just take patches 1,2,3,4 through your tree
>> and let
>> patches 5,6,7 go through arm-soc?
>>
>> There is no compile-time dependency between the two parts, so they
>> will come
>> together nicely in linux-next and during the merge-window.
>>
>>
>> Also in [0] Olof wrote:
>>
>> ----------
>> Traditionally we usually take the DT changes through arm-soc, but as
>> long as we share the branch we might be ok. We tend to stick them in
>> different branches in our tree though, so rockchip will be a little
>> mis-sorted this release. Not a big deal, and we can deal with it.
>> -----------
>>
>> So I'd assume splitting the patchset this way might be a nice solution?
>>
>>
>> Heiko
>>
>>
>> [0] http://www.spinics.net/lists/arm-kernel/msg347053.html
>
> Indeed.
>
> Olof, Arnd ? Will you take the patches 5-6-7 ?


patches 1-4 applied to my tree.

Thanks

   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2014-07-21 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 15:13 [PATCH v10 0/7] arm: Add basic support for Mediatek Cortex-A7 SoCs Matthias Brugger
2014-07-07 15:13 ` [PATCH v10 1/7] of: Provide function to request and map memory Matthias Brugger
2014-07-16 14:26   ` Rob Herring
2014-07-07 15:13 ` [PATCH v10 2/7] clocksource: Add support for the Mediatek SoCs Matthias Brugger
2014-07-07 15:13 ` [PATCH v10 3/7] dt-bindings: add mtk-timer bindings Matthias Brugger
2014-07-07 15:13 ` [PATCH v10 4/7] vendor-prefixes: add prefix for Mediatek Inc Matthias Brugger
2014-07-07 15:13 ` [PATCH v10 5/7] arm: add basic support for Mediatek MT6589 boards Matthias Brugger
2014-07-18  9:46   ` Daniel Lezcano
2014-07-18 10:47     ` Heiko Stübner
2014-07-18 18:56       ` Daniel Lezcano
2014-07-21 13:14         ` Daniel Lezcano [this message]
2014-07-07 15:13 ` [PATCH v10 6/7] dt-bindings: add documentation for Mediatek SoC Matthias Brugger
2014-07-07 15:13 ` [PATCH v10 7/7] arm: mediatek: add dts for Aquaris5 mobile phone Matthias Brugger

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=53CD1228.4050401@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --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).