Hi Thomas, Ingo,

this pull request is an update of the previous one, refreshed against the latest timers/urgent.

* Stephen Boyd hidden the event stream Kconfig option for the arch_arm_timer for non ARM architectures

* Laurent Pinchard fixed a missing a clk_put in case the registering of the sh_mtu[2] drivers fails.

* Uwe Kleine-König reuse clockevents_config_and_register for the at91rm9200_time timer as it was depending on the patch (commit a4578ea (clockevents: Sanitize ticks to nsec conversion)

The following changes since commit 050ded1bbaea3331745cf2782315f5bc2582d083:

  tick: Document tick_do_timer_cpu (2013-11-19 14:59:50 +0100)

are available in the git repository at:

  git://git.linaro.org/people/dlezcano/linux.git clockevents/fixes

for you to fetch changes up to 77f7ce9a9f636daaa65731a833bae1311a7b80e5:

clocksource: arm_arch_timer: Hide eventstream Kconfig on non-ARM (2013-11-21 00:06:52 +0100)

----------------------------------------------------------------
Laurent Pinchart (4):
      clocksource: sh_mtu2: Release clock when sh_mtu2_register() fails
      clocksource: sh_mtu2: Add clk_prepare/unprepare support
      clocksource: sh_tmu: Release clock when sh_tmu_register() fails
      clocksource: sh_tmu: Add clk_prepare/unprepare support

Stephen Boyd (1):
      clocksource: arm_arch_timer: Hide eventstream Kconfig on non-ARM

Uwe Kleine-König (1):
      ARM: at91: rm9200: switch back to clockevents_config_and_register

 arch/arm/mach-at91/at91rm9200_time.c |    7 ++-----
 drivers/clocksource/Kconfig          |    1 +
 drivers/clocksource/sh_mtu2.c        |   16 ++++++++++++++--
 drivers/clocksource/sh_tmu.c         |   20 +++++++++++++++++---
 4 files changed, 34 insertions(+), 10 deletions(-)


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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to