From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] Armada XP clocks for timer
Date: Wed, 04 Sep 2013 10:21:34 +0200 [thread overview]
Message-ID: <5226ED8E.6010308@linaro.org> (raw)
In-Reply-To: <20130903192632.GM19598@titan.lakedaemon.net>
On 09/03/2013 09:26 PM, Jason Cooper wrote:
> On Tue, Sep 03, 2013 at 08:46:33AM -0400, Jason Cooper wrote:
>> On Mon, Sep 02, 2013 at 11:26:26AM -0300, Ezequiel Garcia wrote:
>>> On Tue, Aug 27, 2013 at 05:52:42AM -0300, Ezequiel Garcia wrote:
>>>> Hi Jason and Daniel:
>>>>
>>>> (I forgot to Cc Daniel on these series, sorry about that!)
>>>>
>>>> So, now that we have all the acks we need...
>>>>
>>>> On Tue, Aug 20, 2013 at 12:45:49PM -0300, Ezequiel Garcia wrote:
>>>> [...]
>>>>>
>>>>> Ezequiel Garcia (5):
>>>>> ARM: mvebu: Add the reference 25 MHz fixed-clock to Armada XP
>>>>> ARM: mvebu: Add clock properties to Armada XP timer node
>>>>
>>>> Jason: I assume these are ready to get merged through mvebu, right?
>>>>
>>>>> clocksource: armada-370-xp: Replace WARN_ON with BUG_ON
>>>>> clocksource: armada-370-xp: Get reference fixed-clock by name
>>>>> clocksource: armada-370-xp: Add detailed clock requirements in
>>>>> devicetree binding
>>>>>
>>>>
>>>> Daniel: Will you pick these?
>>>>
>>>> BTW: Is there any chance you can add your clocksource tree to linux-next?
>>>>
>>>> Otherwise, our linux-next builds fail to boot whenever Jason pick some
>>>> mvebu commits and therefore appears in linux-next, but the corresponding
>>>> clocksource commit is taken by you and missing from linux-next.
>>>>
>>>
>>> Daniel,
>>>
>>> Any updates on this? The merge is really close now, and I'd like
>>> to know if you're going to pick these (and where!) for v3.12.
>>>
>>> Notice that Jason already took the devicetree patches, so unless
>>> you merge the clocksource driver changes for v3.12, we'll have
>>> to revert the former.
>>
>> I saw Daniel's pull, so I just sent the last pull for mvebu/dt including
>> these changes.
>
> Daniel, did your changes make it in? If so, I'll have to send these as a
> fix for -rc1...
Not yet.
--
<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
next prev parent reply other threads:[~2013-09-04 8:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 15:45 [PATCH v3 0/5] Armada XP clocks for timer Ezequiel Garcia
2013-08-20 15:45 ` [PATCH v3 1/5] ARM: mvebu: Add the reference 25 MHz fixed-clock to Armada XP Ezequiel Garcia
2013-08-20 19:25 ` Mike Turquette
2013-08-20 15:45 ` [PATCH v3 2/5] ARM: mvebu: Add clock properties to Armada XP timer node Ezequiel Garcia
2013-08-20 19:26 ` Mike Turquette
2013-08-20 15:45 ` [PATCH v3 3/5] clocksource: armada-370-xp: Replace WARN_ON with BUG_ON Ezequiel Garcia
2013-08-20 15:45 ` [PATCH v3 4/5] clocksource: armada-370-xp: Get reference fixed-clock by name Ezequiel Garcia
2013-08-20 15:45 ` [PATCH v3 5/5] clocksource: armada-370-xp: Add detailed clock requirements in devicetree binding Ezequiel Garcia
2013-08-20 20:32 ` Stephen Warren
2013-08-20 20:50 ` Ezequiel Garcia
2013-08-22 8:07 ` [PATCH v3 0/5] Armada XP clocks for timer Gregory CLEMENT
2013-08-27 8:52 ` Ezequiel Garcia
2013-08-27 14:49 ` Jason Cooper
2013-09-02 14:26 ` Ezequiel Garcia
2013-09-03 12:46 ` Jason Cooper
2013-09-03 12:51 ` Ezequiel Garcia
2013-09-03 19:26 ` Jason Cooper
2013-09-04 8:21 ` Daniel Lezcano [this message]
2013-09-11 18:00 ` Ezequiel Garcia
2013-08-27 14:53 ` Jason Cooper
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=5226ED8E.6010308@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).