diff options
author | Arnd Bergmann <arnd@arndb.de> | 2013-04-25 19:28:57 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2013-04-25 20:11:14 +0200 |
commit | 7264a2bbb0a1d9935c653cb0e0cb48cfcaa87538 (patch) | |
tree | 9a72bd158b0b793a3a5a7364a9a9999d03468559 /MAINTAINERS | |
parent | 5eed1987e23c6800050ec61706aeb393b0f0bc96 (diff) | |
download | linux-stable-7264a2bbb0a1d9935c653cb0e0cb48cfcaa87538.tar.gz linux-stable-7264a2bbb0a1d9935c653cb0e0cb48cfcaa87538.tar.bz2 linux-stable-7264a2bbb0a1d9935c653cb0e0cb48cfcaa87538.zip |
cpufreq: pxa2xx: initialize variables
gcc-3.8 correctly found that the variables set by find_freq_tables()
are not initialized if this function is called on something other
than a pxa2xx or pxa3xx:
pxa2xx-cpufreq.c: In function 'pxa_verify_policy':
pxa2xx-cpufreq.c:272:6: warning: 'pxa_freqs_table' may be used uninitialized in this function [-Wmaybe-uninitialized]
pxa2xx-cpufreq.c: In function 'pxa_set_target':
pxa2xx-cpufreq.c:345:23: warning: 'pxa_freq_settings' may be used uninitialized in this function [-Wmaybe-uninitialized]
Rather than adding a bogus initialization that would let us
get a little further before crashing, add an explicit BUG().
We know that this code is designed to run on only these cpus,
so this will fix the build warning and give a more helpful
diagnostic if the code ever changes to run on other machines.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions