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: [GIT PULL]clocksource: dw_apb_timer_of: Fix read_sched_clock
Date: Sun, 24 Nov 2013 22:53:33 +0100	[thread overview]
Message-ID: <5292755D.3050000@linaro.org> (raw)
In-Reply-To: <52917B22.3040205@gmail.com>

On 11/24/2013 05:05 AM, Dinh Nguyen wrote:
> Hi Daniel,
>
> On 10/7/13 2:18 PM, Daniel Lezcano wrote:
>> On 10/07/2013 07:10 PM, John Stultz wrote:
>>> On 10/07/2013 09:09 AM, Daniel Lezcano wrote:
>>>> On 10/07/2013 05:27 PM, dinguyen at altera.com wrote:
>>>>> From: Dinh Nguyen <dinguyen@altera.com>
>>>>>
>>>>> Hi Thomas, John,
>>>>>
>>>>> I am hoping you can pull in these 2 patches. These 2 patches have
>>>>> been floating
>>>>> around for almost 2 months now. They are needed to get the Altera
>>>>> SOCFPGA
>>>>> booting again because of a DTS binding change in 3.12.
>>>>>
>>>>> The other change was correctly return the current clock counter.
>>>>>
>>>>> The discussion thread can be found here:
>>>>>
>>>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-September/198818.html
>>>>>
>>>>>
>>>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-September/198903.html
>>>>>
>>>>>
>>>>>
>>>>> This patch does not attempt or change the behaviour of the ordering
>>>>> of how a
>>>>> clocksource or clockevent is use. These 2 patches only enables a
>>>>> platform to boot.
>>>>
>>>> John,
>>>>
>>>> I agree with Dinh, these patches fixes a boot issue on Altera SOCFPGA
>>>> and should be merged.
>>>>
>>>
>>> Hey Dinh,
>>>       Thanks for persisting here! Sorry this has taken awhile. Just as an
>>> FYI, Daniel is maintaining the drivers/clocksource dir these days.
>>>
>>> So, I've not been following this closely, but if I recall we had a merge
>>> conflict that we backed out, since it seemed that everyone involved in
>>> this driver weren't working together. Then Thomas had some objections,
>>> but it *looks* like that's been resolved. So I don't have any objections
>>> at this point.
>>
>> Yeah, it happens the same to me :)
>>
>>> Daniel: if you want to pull these in to your tree, that's fine by me.
>>
>> Ok, pulled to my tree.
> I did not see these 2 patches in 3.13-rc1. Just wondering what happened
> to them?

Me too :/

I will take them for 3.13 fixes.


-- 
  <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:[~2013-11-24 21:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 15:27 [GIT PULL]clocksource: dw_apb_timer_of: Fix read_sched_clock dinguyen at altera.com
2013-10-07 16:09 ` Daniel Lezcano
2013-10-07 17:10   ` John Stultz
2013-10-07 19:18     ` Daniel Lezcano
2013-11-24  4:05       ` Dinh Nguyen
2013-11-24 21:53         ` Daniel Lezcano [this message]

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=5292755D.3050000@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).