From: kbuild test robot <fengguang.wu@intel.com>
To: Maria Dimakopoulou <maria.n.dimakopoulou@gmail.com>
Cc: kbuild-all@01.org, Peter Zijlstra <peterz@infradead.org>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [peterz-queue:master 2112/2183] arch/x86/kernel/cpu/perf_event_intel.c:2204:25: sparse: symbol 'allocate_excl_cntrs' was not declared. Should it be static?
Date: Tue, 31 Mar 2015 21:32:13 +0800 [thread overview]
Message-ID: <201503312102.HyyNbQ5j%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git master
head: dc457a0288847522525701d01c1d43d564d06132
commit: cafb328c12993896509de8309f9874949f64e5a4 [2112/2183] perf/x86: add cross-HT counter exclusion infrastructure
reproduce:
# apt-get install sparse
git checkout cafb328c12993896509de8309f9874949f64e5a4
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
arch/x86/kernel/cpu/perf_event_intel.c:196:18: sparse: symbol 'nhm_events_attrs' was not declared. Should it be static?
arch/x86/kernel/cpu/perf_event_intel.c:201:18: sparse: symbol 'snb_events_attrs' was not declared. Should it be static?
arch/x86/kernel/cpu/perf_event_intel.c:223:25: sparse: symbol 'intel_bdw_event_constraints' was not declared. Should it be static?
>> arch/x86/kernel/cpu/perf_event_intel.c:2204:25: sparse: symbol 'allocate_excl_cntrs' was not declared. Should it be static?
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
next reply other threads:[~2015-03-31 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 13:32 kbuild test robot [this message]
2015-03-31 13:32 ` [PATCH peterz-queue] perf/x86: allocate_excl_cntrs() can be static 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=201503312102.HyyNbQ5j%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=acme@kernel.org \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maria.n.dimakopoulou@gmail.com \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®