summaryrefslogtreecommitdiff
path: root/arch/xtensa
diff options
context:
space:
mode:
authorPrarit Bhargava <prarit@redhat.com>2009-11-12 09:18:46 -0500
committerDave Jones <davej@redhat.com>2009-11-17 23:15:04 -0500
commit90e41bac100e34f955f48e7686c2fc685ac9aa30 (patch)
tree50ae248a292e85d3e784d12e2e6a37823048d98b /arch/xtensa
parent54c9a35d9faef06e00e2a941eb8fe674f1886901 (diff)
downloadlinux-exynos-90e41bac100e34f955f48e7686c2fc685ac9aa30.tar.gz
linux-exynos-90e41bac100e34f955f48e7686c2fc685ac9aa30.tar.bz2
linux-exynos-90e41bac100e34f955f48e7686c2fc685ac9aa30.zip
[CPUFREQ] Fix stale cpufreq_cpu_governor pointer
Dave, Attached is an update of my patch against the cpufreq fixes branch. Before applying the patch I compiled and booted the tree to see if the panic was still there -- to my surprise it was not. This is because of the conversion of cpufreq_cpu_governor to a char[]. While the panic is kaput, the problem of stale data continues and my patch is still valid. It is possible to end up with the wrong governor after hotplug events because CPUFREQ_DEFAULT_GOVERNOR is statically linked to a default, while the cpu siblings may have had a different governor assigned by a user. ie) the patch is still needed in order to keep the governors assigned properly when hotplugging devices Signed-off-by: Prarit Bhargava <prarit@redhat.com> Signed-off-by: Dave Jones <davej@redhat.com>
Diffstat (limited to 'arch/xtensa')
0 files changed, 0 insertions, 0 deletions