diff options
author | Borislav Petkov <bp@suse.de> | 2015-04-03 15:19:53 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-04-15 23:02:24 +0200 |
commit | 64df1fdfccc054a4e5480c6bc965b67d3c83c3ae (patch) | |
tree | 3501943d155ed9b2e5a350e45e32635da0ba9a70 /tools | |
parent | 6a82ba6d4fda21e5f9fda0f4126add3b88522f02 (diff) | |
download | linux-stable-64df1fdfccc054a4e5480c6bc965b67d3c83c3ae.tar.gz linux-stable-64df1fdfccc054a4e5480c6bc965b67d3c83c3ae.tar.bz2 linux-stable-64df1fdfccc054a4e5480c6bc965b67d3c83c3ae.zip |
cpufreq: intel_pstate: Fix an annoying !CONFIG_SMP warning
I keep seeing
drivers/cpufreq/intel_pstate.c: In function ‘intel_pstate_init’:
drivers/cpufreq/intel_pstate.c:1187:26: warning: initialization from incompatible pointer type
struct cpuinfo_x86 *c = &boot_cpu_data;
when doing randconfig builds.
This is caused by the fact that when !CONFIG_SMP, asm/processor.h
defines cpu_info to boot_cpu_data and the local variable
struct cpu_defaults *cpu_info
overshadows it leading to this unfortunate assignment in the
preprocessed source:
struct cpu_defaults *boot_cpu_data;
struct cpuinfo_x86 *c = &boot_cpu_data;
Rename the local variable and use static_cpu_has_safe() which alleviates
the need for defining a local cpuinfo_x86 pointer.
Signed-off-by: Borislav Petkov <bp@suse.de>
Acked-by: Kristen Carlson Accardi <kristen@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions