On Fri, Sep 13, 2013 at 06:32:07PM +0530, Viresh Kumar wrote: > + read_lock_irqsave(&cpufreq_driver_lock, flags); > + notify = !(cpufreq_driver->flags & CPUFREQ_ASYNC_NOTIFICATION); > + read_unlock_irqrestore(&cpufreq_driver_lock, flags); I don't think this needs to be read under a lock - if this bit changes dynamically, then there's something very wrong. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
