From: kernel test robot <lkp@intel.com>
To: Guo Ren <guoren@linux.alibaba.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 3483/12125] arch/csky/kernel/perf_event.c:90:10: warning: no previous prototype for 'csky_pmu_read_cc'
Date: Tue, 23 Feb 2021 20:39:56 +0800 [thread overview]
Message-ID: <202102232052.sPPbCTzl-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2664 bytes --]
Hi Guo,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8431fb50e1a7ffe7fcc4da2f798d3100315cee7b
commit: 8d1733b612c9576ec3ff96491cffcb40ad756c1c [3483/12125] csky: Add VDSO with GENERIC_GETTIMEOFDAY, GENERIC_TIME_VSYSCALL, HAVE_GENERIC_VDSO
config: csky-randconfig-r002-20210223 (attached as .config)
compiler: csky-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8d1733b612c9576ec3ff96491cffcb40ad756c1c
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 8d1733b612c9576ec3ff96491cffcb40ad756c1c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=csky
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/csky/kernel/perf_event.c:90:10: warning: no previous prototype for 'csky_pmu_read_cc' [-Wmissing-prototypes]
90 | uint64_t csky_pmu_read_cc(void)
| ^~~~~~~~~~~~~~~~
arch/csky/kernel/perf_event.c:878:6: warning: no previous prototype for 'csky_pmu_event_set_period' [-Wmissing-prototypes]
878 | int csky_pmu_event_set_period(struct perf_event *event)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
arch/csky/kernel/perf_event.c:1198:5: warning: no previous prototype for 'init_hw_perf_events' [-Wmissing-prototypes]
1198 | int init_hw_perf_events(void)
| ^~~~~~~~~~~~~~~~~~~
arch/csky/kernel/perf_event.c:1293:5: warning: no previous prototype for 'csky_pmu_device_probe' [-Wmissing-prototypes]
1293 | int csky_pmu_device_probe(struct platform_device *pdev,
| ^~~~~~~~~~~~~~~~~~~~~
vim +/csky_pmu_read_cc +90 arch/csky/kernel/perf_event.c
88
89 /* cycle counter */
> 90 uint64_t csky_pmu_read_cc(void)
91 {
92 uint32_t lo, hi, tmp;
93 uint64_t result;
94
95 do {
96 tmp = cprgr("<0, 0x3>");
97 lo = cprgr("<0, 0x2>");
98 hi = cprgr("<0, 0x3>");
99 } while (hi != tmp);
100
101 result = (uint64_t) (hi) << 32;
102 result |= lo;
103
104 return result;
105 }
106
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33347 bytes --]
reply other threads:[~2021-02-23 12:40 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=202102232052.sPPbCTzl-lkp@intel.com \
--to=lkp@intel.com \
--cc=guoren@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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