On Tue, 25 Sep 2012, Tero Kristo wrote: > Previously the code only acquired spinlock after increasing / decreasing > the usecount value, which is wrong. This leaves a small window where > a task switch may occur between the check of the usecount and the actual > wakeup / sleep of the domain. Fixed by moving the spinlock locking before > the usecount access. Left the usecount as atomic_t if someone wants an > easy access to the parameter through atomic_read. > > Signed-off-by: Tero Kristo <t-kristo@xxxxxx> Acked-by: Paul Walmsley <paul@xxxxxxxxx> - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html