diff options
author | Viresh Kumar <viresh.kumar@linaro.org> | 2015-06-08 18:25:29 +0530 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-06-11 01:01:54 +0200 |
commit | 2fc3384dc75bf7333384c7a16d12c796f61c3f56 (patch) | |
tree | f5c7146445748ccf9dbd004d518301d7fcc6e326 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 87549141d516aee71d511138e27117c41e8aef68 (diff) |
cpufreq: Initialize policy->kobj while allocating policy
policy->kobj is required to be initialized once in the lifetime of a
policy. Currently we are initializing it from __cpufreq_add_dev() and
that doesn't look to be the best place for doing so as we have to do
this on special cases (like: !recover_policy).
We can initialize it from a more obvious place cpufreq_policy_alloc()
and that will make code look cleaner, specially the error handling part.
The error handling part of __cpufreq_add_dev() was doing almost the same
thing while recover_policy is true or false. Fix that as well by always
calling cpufreq_policy_put_kobj() with an additional parameter to skip
notification part of it.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions