* [PATCH tip] perf: perf_mux_hrtimer_cancel() can be static
2015-04-22 20:00 [tip:timers/core 44/44] kernel/events/core.c:776:6: sparse: symbol 'perf_mux_hrtimer_cancel' was not declared. Should it be static? kbuild test robot
@ 2015-04-22 20:00 ` kbuild test robot
2015-04-22 20:09 ` [tip:timers/core] " tip-bot for kbuild test robot
0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2015-04-22 20:00 UTC (permalink / raw)
To: Peter Zijlstra
Cc: kbuild-all, Thomas Gleixner, Paul Mackerras, Ingo Molnar,
Arnaldo Carvalho de Melo, linux-kernel
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index e7ed00b..598182d 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -773,7 +773,7 @@ static enum hrtimer_restart perf_mux_hrtimer_handler(struct hrtimer *hr)
}
/* CPU is going down */
-void perf_mux_hrtimer_cancel(int cpu)
+static void perf_mux_hrtimer_cancel(int cpu)
{
struct perf_cpu_context *cpuctx;
struct pmu *pmu;
^ permalink raw reply [flat|nested] 3+ messages in thread
* [tip:timers/core 44/44] kernel/events/core.c:776:6: sparse: symbol 'perf_mux_hrtimer_cancel' was not declared. Should it be static?
@ 2015-04-22 20:00 kbuild test robot
2015-04-22 20:00 ` [PATCH tip] perf: perf_mux_hrtimer_cancel() can be static kbuild test robot
0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2015-04-22 20:00 UTC (permalink / raw)
To: Peter Zijlstra
Cc: kbuild-all, Thomas Gleixner, Paul Mackerras, Ingo Molnar,
Arnaldo Carvalho de Melo, linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [tip:timers/core] perf: perf_mux_hrtimer_cancel() can be static
2015-04-22 20:00 ` [PATCH tip] perf: perf_mux_hrtimer_cancel() can be static kbuild test robot
@ 2015-04-22 20:09 ` tip-bot for kbuild test robot
0 siblings, 0 replies; 3+ messages in thread
From: tip-bot for kbuild test robot @ 2015-04-22 20:09 UTC (permalink / raw)
To: linux-tip-commits
Cc: paulus, linux-kernel, acme, mingo, tglx, peterz, hpa, fengguang.wu
Commit-ID: 9183034879a1196714836c8142340c850c747323
Gitweb: http://git.kernel.org/tip/9183034879a1196714836c8142340c850c747323
Author: kbuild test robot <fengguang.wu@intel.com>
AuthorDate: Thu, 23 Apr 2015 04:00:00 +0800
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Wed, 22 Apr 2015 22:06:34 +0200
perf: perf_mux_hrtimer_cancel() can be static
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Cc: kbuild-all@01.org
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/20150422200000.GA122603@lkp-sb04
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
kernel/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index e7ed00b..598182d 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -773,7 +773,7 @@ static enum hrtimer_restart perf_mux_hrtimer_handler(struct hrtimer *hr)
}
/* CPU is going down */
-void perf_mux_hrtimer_cancel(int cpu)
+static void perf_mux_hrtimer_cancel(int cpu)
{
struct perf_cpu_context *cpuctx;
struct pmu *pmu;
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-04-22 20:10 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-22 20:00 [tip:timers/core 44/44] kernel/events/core.c:776:6: sparse: symbol 'perf_mux_hrtimer_cancel' was not declared. Should it be static? kbuild test robot
2015-04-22 20:00 ` [PATCH tip] perf: perf_mux_hrtimer_cancel() can be static kbuild test robot
2015-04-22 20:09 ` [tip:timers/core] " tip-bot for kbuild test robot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®