All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] arm: dts: keystone: add keystone timer entry
Date: Mon, 13 Jan 2014 14:14:33 +0100	[thread overview]
Message-ID: <52D3E6B9.40502@linaro.org> (raw)
In-Reply-To: <52D3CDD5.9060104@ti.com>

On 01/13/2014 12:28 PM, ivan.khoronzhuk wrote:
> On 12/28/2013 09:07 PM, Daniel Lezcano wrote:
>> On 12/26/2013 07:02 PM, Santosh Shilimkar wrote:
>>> $subject
>>> s/arm/ARM,
>>>
>>> On Wednesday 25 December 2013 07:32 AM, Ivan Khoronzhuk wrote:
>>>> Add keystone timer entry to keystone device tree.
>>>> This 64-bit timer is used as backup clock event device.
>>>>
>>>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
>>>> ---
>>> No need to repost. I will fix it up while applying based
>>> on state of PATCH 1/3 and 2/3.
>>
>> I assume you will take the patchset in your tree.
>>
>> I am back from vacations, give me a couple of days to review the
>> patchset before applying it please.
>>
>> Thanks
>>    -- Daniel
>>
>
> Hi, Daniel
>
> Do you have any comments on this patch series?
> Can we expect it in k3.14

I have applied the patch 1/3 and 2/3 in my tree but I was expecting the 
DT folks to give their acked-by for the patch 2/3.

It is a bit late for 3.14 but if the patch 3/3 is in Santosh's tree, the 
patch 2/3 gets its acked-by and you absolutely need the driver for this 
version, I may consider to send another PR to the upstream maintainers. 
That will be up to them to accept to pull it or not.

-- 
  <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-01-13 13:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25 12:32 [PATCH v3 0/3] Introduce clocksource driver for Keystone platform Ivan Khoronzhuk
2013-12-25 12:32 ` [PATCH v3 1/3] clocksource: timer-keystone: introduce clocksource driver for Keystone Ivan Khoronzhuk
2013-12-26 17:58   ` Santosh Shilimkar
2013-12-26 18:22   ` Stephen Boyd
2013-12-26 18:40     ` ivan.khoronzhuk
2013-12-26 19:42       ` Stephen Boyd
2013-12-25 12:32 ` [PATCH v3 2/3] clocksource: keystone: add bindings for keystone timer Ivan Khoronzhuk
2013-12-26 18:00   ` Santosh Shilimkar
2013-12-25 12:32 ` [PATCH v3 3/3] arm: dts: keystone: add keystone timer entry Ivan Khoronzhuk
2013-12-26 18:02   ` Santosh Shilimkar
2013-12-28 19:07     ` Daniel Lezcano
2013-12-29 19:23       ` Santosh Shilimkar
2014-01-13 11:28       ` ivan.khoronzhuk
2014-01-13 13:14         ` Daniel Lezcano [this message]
2014-01-13 14:20           ` Santosh Shilimkar

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=52D3E6B9.40502@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 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.