cpufreq: remove policy->governor setting in drivers initialization
As policy->governor is already set to CPUFREQ_DEFAULT_GOVERNOR in the (always built-in) cpufreq core, we do not need to set it in the drivers. This fixes the sparc64 allmodconfig build failure. Also, remove a totally useles setting of ->policy in cpufreq-pxa3xx.c. Signed-off-by:Dominik Brodowski <linux@dominikbrodowski.net> Acked-by:
David S. Miller <davem@davemloft.net> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
Showing
- arch/arm/mach-integrator/cpu.c 0 additions, 1 deletionarch/arm/mach-integrator/cpu.c
- arch/arm/mach-pxa/cpufreq-pxa2xx.c 0 additions, 3 deletionsarch/arm/mach-pxa/cpufreq-pxa2xx.c
- arch/arm/mach-pxa/cpufreq-pxa3xx.c 0 additions, 1 deletionarch/arm/mach-pxa/cpufreq-pxa3xx.c
- arch/arm/mach-sa1100/cpu-sa1100.c 0 additions, 1 deletionarch/arm/mach-sa1100/cpu-sa1100.c
- arch/avr32/mach-at32ap/cpufreq.c 0 additions, 1 deletionarch/avr32/mach-at32ap/cpufreq.c
- arch/blackfin/mach-common/cpufreq.c 0 additions, 2 deletionsarch/blackfin/mach-common/cpufreq.c
- arch/cris/arch-v32/mach-a3/cpufreq.c 0 additions, 1 deletionarch/cris/arch-v32/mach-a3/cpufreq.c
- arch/cris/arch-v32/mach-fs/cpufreq.c 0 additions, 1 deletionarch/cris/arch-v32/mach-fs/cpufreq.c
- arch/sparc64/kernel/us3_cpufreq.c 0 additions, 1 deletionarch/sparc64/kernel/us3_cpufreq.c
Loading
Please register or sign in to comment