[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201508112018.CEFIP2Xy%fengguang.wu@intel.com>
Date: Tue, 11 Aug 2015 20:08:31 +0800
From: kbuild test robot <fengguang.wu@...el.com>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>
Cc: kbuild-all@...org, David Vrabel <david.vrabel@...rix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
xen-devel@...ts.xenproject.org, linux-kernel@...r.kernel.org
Subject: [xen-tip:linux-next 21/23] arch/x86/xen/pmu.c:211:20: sparse: symbol
'xen_amd_read_pmc' was not declared. Should it be static?
tree: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip linux-next
head: 0d26d72cab825a0227c8d8e0e42161125b3116fd
commit: 80ef65bb2362fd9eedcb4ec1d41d8a6d0b99dfbb [21/23] xen/PMU: Intercept PMU-related MSR and APIC accesses
reproduce:
# apt-get install sparse
git checkout 80ef65bb2362fd9eedcb4ec1d41d8a6d0b99dfbb
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
arch/x86/xen/pmu.c:18:1: sparse: symbol '__pcpu_scope_xenpmu_shared' was not declared. Should it be static?
>> arch/x86/xen/pmu.c:211:20: sparse: symbol 'xen_amd_read_pmc' was not declared. Should it be static?
>> arch/x86/xen/pmu.c:220:20: sparse: symbol 'xen_intel_read_pmc' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists