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] clocksource: arm_global_timer: register delay timer
Date: Tue, 16 Feb 2016 11:42:25 +0000	[thread overview]
Message-ID: <56C30B21.4000707@linaro.org> (raw)
In-Reply-To: <20160216112841.GA26773@axis.com>

On 02/16/2016 11:28 AM, Rabin Vincent wrote:
> On Thu, Aug 20, 2015 at 09:03:04PM +0200, Daniel Lezcano wrote:
>> On 08/19/2015 03:43 PM, Rabin Vincent wrote:
>>> Provide a delay timer using the lower 32-bits of the global timer so
>>> that we can use that instead of having to calibrating delays.
>>>
>>> Signed-off-by: Rabin Vincent <rabin.vincent@axis.com>
>>
>> Applied to my tree for 4.4
>
> This seems to have got lost?  I don't see it in v4.4 or current mainline
> (v4.5-rc4).  It still applies cleanly.

Oops, right.

Fixed now [1]. Thanks for the heads up.

   -- Daniel

[1] 
https://git.linaro.org/people/daniel.lezcano/linux.git/commit/23cb25d0f407e83be10747258092843e8e20d535

-- 
  <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

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Rabin Vincent <rabin.vincent@axis.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"srinivas.kandagatla@gmail.com" <srinivas.kandagatla@gmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clocksource: arm_global_timer: register delay timer
Date: Tue, 16 Feb 2016 11:42:25 +0000	[thread overview]
Message-ID: <56C30B21.4000707@linaro.org> (raw)
In-Reply-To: <20160216112841.GA26773@axis.com>

On 02/16/2016 11:28 AM, Rabin Vincent wrote:
> On Thu, Aug 20, 2015 at 09:03:04PM +0200, Daniel Lezcano wrote:
>> On 08/19/2015 03:43 PM, Rabin Vincent wrote:
>>> Provide a delay timer using the lower 32-bits of the global timer so
>>> that we can use that instead of having to calibrating delays.
>>>
>>> Signed-off-by: Rabin Vincent <rabin.vincent@axis.com>
>>
>> Applied to my tree for 4.4
>
> This seems to have got lost?  I don't see it in v4.4 or current mainline
> (v4.5-rc4).  It still applies cleanly.

Oops, right.

Fixed now [1]. Thanks for the heads up.

   -- Daniel

[1] 
https://git.linaro.org/people/daniel.lezcano/linux.git/commit/23cb25d0f407e83be10747258092843e8e20d535

-- 
  <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:[~2016-02-16 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 13:43 [PATCH] clocksource: arm_global_timer: register delay timer Rabin Vincent
2015-08-19 13:43 ` Rabin Vincent
2015-08-20 19:03 ` Daniel Lezcano
2015-08-20 19:03   ` Daniel Lezcano
2016-02-16 11:28   ` Rabin Vincent
2016-02-16 11:28     ` Rabin Vincent
2016-02-16 11:42     ` Daniel Lezcano [this message]
2016-02-16 11:42       ` Daniel Lezcano

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=56C30B21.4000707@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.