diff options
author | Josh Triplett <josh@joshtriplett.org> | 2013-08-20 17:20:15 -0700 |
---|---|---|
committer | Len Brown <len.brown@intel.com> | 2014-01-18 22:34:09 -0500 |
commit | 74823419761c11830ea1819365f82cf3d48795cb (patch) | |
tree | ac323646d9af59a412b2e8bdf981dd803b806faf /kernel | |
parent | 2b92865e648ce04a39fda4f903784a5d01ecb0dc (diff) | |
download | linux-74823419761c11830ea1819365f82cf3d48795cb.tar.bz2 |
turbostat: Check return value of fscanf
Some systems declare fscanf with the warn_unused_result attribute. On
such systems, turbostat generates the following warnings:
turbostat.c: In function 'get_core_id':
turbostat.c:1203:8: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
turbostat.c: In function 'get_physical_package_id':
turbostat.c:1186:8: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
turbostat.c: In function 'cpu_is_first_core_in_package':
turbostat.c:1169:8: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
turbostat.c: In function 'cpu_is_first_sibling_in_core':
turbostat.c:1148:8: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
Fix these by checking the return value of those four calls to fscanf.
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions