Messages in this thread | | | Date | Wed, 26 Feb 2014 11:44:04 +0530 | Subject | Re: [PATCH 3/3] cpufreq: Set policy to non-NULL only after all hotplug online work is done | From | Viresh Kumar <> |
| |
On 26 February 2014 09:08, Saravana Kannan <skannan@codeaurora.org> wrote: > The existing code sets the per CPU policy to a non-NULL value before all > the steps performed during the hotplug online path is done. Specifically, > this is done before the policy min/max, governors, etc are initialized for > the policy. This in turn means that calls to cpufreq_cpu_get() return a > non-NULL policy before the policy/CPU is ready to be used.
First two patches are fine but I would still say that take the three patches I posted instead of this. Reasoning already given in other mails.
| |