From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clocksource: Provide timekeeping for efm32 SoCs
Date: Tue, 22 Oct 2013 23:00:33 +0200 [thread overview]
Message-ID: <5266E771.4070906@linaro.org> (raw)
In-Reply-To: <20131022201001.GB27227@pengutronix.de>
On 10/22/2013 10:10 PM, Uwe Kleine-K?nig wrote:
> On Tue, Oct 08, 2013 at 04:51:47PM +0200, Uwe Kleine-K?nig wrote:
>> Hello Daniel,
>>
>> On Tue, Oct 08, 2013 at 01:30:15PM +0200, Daniel Lezcano wrote:
>>> On 10/03/2013 09:56 PM, Uwe Kleine-K?nig wrote:
>>>> An efm32 features 4 16-bit timers with a 10-bit prescaler. This driver
>>>> provides clocksource and clock event device using one timer instance
>>>> each.
>>>>
>>>> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
>>>> ---
>>>
>>> Applied to my tree for 3.13
>> Thanks
> Where is your tree to be found? This commit isn't in
>
> git://git.linaro.org/people/dlezcano/linux.git clockevents/3.13
>
> and also it's not included in next-20131021.
Thanks for the heads up.
I synced my local tree with the tree:
git://git.linaro.org/people/dlezcano/linux.git
for the branch clockevents/3.13 and clockevents/3.12-fixes
I will send a PR as soon as I can.
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
prev parent reply other threads:[~2013-10-22 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 19:56 [PATCH v2] clocksource: Provide timekeeping for efm32 SoCs Uwe Kleine-König
2013-10-08 11:30 ` Daniel Lezcano
2013-10-08 14:51 ` Uwe Kleine-König
2013-10-22 20:10 ` Uwe Kleine-König
2013-10-22 21:00 ` 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=5266E771.4070906@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).