https://github.com/torvalds/linux
Revision 65ada547d68dc075aa06df92fe325bff07cbc606 authored by Takashi YOSHII on 17 December 2010, 07:25:09 UTC, committed by Paul Mundt on 17 December 2010, 10:38:33 UTC
There are control flow that sh_cmt_set_next() does double
spin-lock. The callers sh_cmt_{start,stop}() already have
lock. But another callers sh_cmt_clock_event_{start,next}()
does not.

Now sh_cmt_set_next() does not lock by itself. All the
callers should hold spin-lock before calling it.

[damm@opensource.se: use __sh_cmt_set_next() to simplify code]
[damm@opensource.se: added stable, suitable for v2.6.35 + v2.6.36]
Cc: stable@kernel.org
Signed-off-by: Takashi YOSHII <takashi.yoshii.zj@renesas.com>
Signed-off-by: Magnus Damm <damm@opensource.se>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
1 parent b3444d1
History
Tip revision: 65ada547d68dc075aa06df92fe325bff07cbc606 authored by Takashi YOSHII on 17 December 2010, 07:25:09 UTC
clocksource: sh_cmt: Remove nested spinlock fix
Tip revision: 65ada54

README.AddingFirmware

back to top