From: kbuild test robot <fengguang.wu@intel.com>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 12436/12894] drivers//perf/arm_dsu_pmu.c:661:2: error: implicit declaration of function 'bitmap_from_u32array'; did you mean 'bitmap_from_arr32'?
Date: Mon, 5 Feb 2018 22:57:03 +0800 [thread overview]
Message-ID: <201802052200.wqb0nNTE%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3244 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: a352043b40947d6253b87993cb24ee0f893aad89
commit: 39461af74125fd26809486d043f248531e17a2e5 [12436/12894] bitmap: replace bitmap_{from,to}_u32array
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 39461af74125fd26809486d043f248531e17a2e5
# save the attached .config to linux build tree
make.cross ARCH=arm64
All errors (new ones prefixed by >>):
drivers//perf/arm_dsu_pmu.c: In function 'dsu_pmu_probe_pmu':
>> drivers//perf/arm_dsu_pmu.c:661:2: error: implicit declaration of function 'bitmap_from_u32array'; did you mean 'bitmap_from_arr32'? [-Werror=implicit-function-declaration]
bitmap_from_u32array(dsu_pmu->cpmceid_bitmap,
^~~~~~~~~~~~~~~~~~~~
bitmap_from_arr32
cc1: some warnings being treated as errors
vim +661 drivers//perf/arm_dsu_pmu.c
7520fa99 Suzuki K Poulose 2018-01-02 642
7520fa99 Suzuki K Poulose 2018-01-02 643 /*
7520fa99 Suzuki K Poulose 2018-01-02 644 * dsu_pmu_probe_pmu: Probe the PMU details on a CPU in the cluster.
7520fa99 Suzuki K Poulose 2018-01-02 645 */
7520fa99 Suzuki K Poulose 2018-01-02 646 static void dsu_pmu_probe_pmu(struct dsu_pmu *dsu_pmu)
7520fa99 Suzuki K Poulose 2018-01-02 647 {
7520fa99 Suzuki K Poulose 2018-01-02 648 u64 num_counters;
7520fa99 Suzuki K Poulose 2018-01-02 649 u32 cpmceid[2];
7520fa99 Suzuki K Poulose 2018-01-02 650
7520fa99 Suzuki K Poulose 2018-01-02 651 num_counters = (__dsu_pmu_read_pmcr() >> CLUSTERPMCR_N_SHIFT) &
7520fa99 Suzuki K Poulose 2018-01-02 652 CLUSTERPMCR_N_MASK;
7520fa99 Suzuki K Poulose 2018-01-02 653 /* We can only support up to 31 independent counters */
7520fa99 Suzuki K Poulose 2018-01-02 654 if (WARN_ON(num_counters > 31))
7520fa99 Suzuki K Poulose 2018-01-02 655 num_counters = 31;
7520fa99 Suzuki K Poulose 2018-01-02 656 dsu_pmu->num_counters = num_counters;
7520fa99 Suzuki K Poulose 2018-01-02 657 if (!dsu_pmu->num_counters)
7520fa99 Suzuki K Poulose 2018-01-02 658 return;
7520fa99 Suzuki K Poulose 2018-01-02 659 cpmceid[0] = __dsu_pmu_read_pmceid(0);
7520fa99 Suzuki K Poulose 2018-01-02 660 cpmceid[1] = __dsu_pmu_read_pmceid(1);
7520fa99 Suzuki K Poulose 2018-01-02 @661 bitmap_from_u32array(dsu_pmu->cpmceid_bitmap,
7520fa99 Suzuki K Poulose 2018-01-02 662 DSU_PMU_MAX_COMMON_EVENTS,
7520fa99 Suzuki K Poulose 2018-01-02 663 cpmceid,
7520fa99 Suzuki K Poulose 2018-01-02 664 ARRAY_SIZE(cpmceid));
7520fa99 Suzuki K Poulose 2018-01-02 665 }
7520fa99 Suzuki K Poulose 2018-01-02 666
:::::: The code at line 661 was first introduced by commit
:::::: 7520fa99246dade7ab6dde1573a146beed632abd perf: ARM DynamIQ Shared Unit PMU support
:::::: TO: Suzuki K Poulose <suzuki.poulose@arm.com>
:::::: CC: Will Deacon <will.deacon@arm.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 58659 bytes --]
reply other threads:[~2018-02-05 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201802052200.wqb0nNTE%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=ynorov@caviumnetworks.com \
/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