tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core head: 272325c4821f052092c41feac21f4a1a46f0ad48 commit: 272325c4821f052092c41feac21f4a1a46f0ad48 [44/44] perf: Fix mux_interval hrtimer wreckage reproduce: # apt-get install sparse git checkout 272325c4821f052092c41feac21f4a1a46f0ad48 make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>) kernel/events/core.c:324:26: sparse: function 'perf_pmu_name' with external linkage has definition kernel/events/core.c:198:6: sparse: symbol 'update_perf_cpu_limits' was not declared. Should it be static? kernel/events/core.c:494:26: sparse: incorrect type in initializer (different address spaces) kernel/events/core.c:494:26: expected void const [noderef] <asn:3>*__vpp_verify kernel/events/core.c:494:26: got struct perf_cpu_context *<noident> kernel/events/core.c:474:6: sparse: symbol 'perf_cgroup_switch' was not declared. Should it be static? kernel/events/core.c:790:26: sparse: incorrect type in initializer (different address spaces) kernel/events/core.c:790:26: expected void const [noderef] <asn:3>*__vpp_verify kernel/events/core.c:790:26: got struct perf_cpu_context *<noident> >> kernel/events/core.c:776:6: sparse: symbol 'perf_mux_hrtimer_cancel' was not >> declared. Should it be static? kernel/events/core.c:845:22: sparse: incorrect type in initializer (different address spaces) kernel/events/core.c:845:22: expected void const [noderef] <asn:3>*__vpp_verify kernel/events/core.c:845:22: got int *<noident> kernel/events/core.c:852:22: sparse: incorrect type in initializer (different address spaces) kernel/events/core.c:852:22: expected void const [noderef] <asn:3>*__vpp_verify kernel/events/core.c:852:22: got int *<noident> kernel/events/core.c:1065:15: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:1078:28: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:2522:18: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:2523:23: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:4189:14: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:4222:14: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:4278:14: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:4351:14: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:4372:14: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:5465:23: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:6274:17: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:6294:17: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:6420:16: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:6431:9: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:6420:16: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:6629:23: sparse: incompatible types in comparison expression (different address spaces) kernel/events/core.c:8401:21: sparse: incompatible types in comparison expression (different address spaces) Please review and possibly fold the followup patch. --- 0-DAY kernel test infrastructure Open Source Technology Center http://lists.01.org/mailman/listinfo/kbuild Intel Corporation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
