mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@01.org, Thomas Gleixner <tglx@linutronix.de>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [tip:timers/core 44/44] kernel/events/core.c:776:6: sparse: symbol 'perf_mux_hrtimer_cancel' was not declared. Should it be static?
Date: Thu, 23 Apr 2015 04:00:00 +0800	[thread overview]
Message-ID: <201504230349.4qd8rvFe%fengguang.wu@intel.com> (raw)

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

             reply	other threads:[~2015-04-22 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 20:00 kbuild test robot [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201504230349.4qd8rvFe%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=acme@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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®