From: kbuild test robot <fengguang.wu@intel.com>
To: Milind Chabbi <chabbi.milind@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>,
Jiri Olsa <jolsa@kernel.org>
Subject: [tip:perf/core 36/37] kernel/events/core.c:2856:8: error: implicit declaration of function 'modify_user_hw_breakpoint_check'; did you mean 'modify_user_hw_breakpoint'?
Date: Tue, 13 Mar 2018 15:29:23 +0800 [thread overview]
Message-ID: <201803131516.0ze2DEoS%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
head: 5acc575fec9f424f0b557844dbda8aed57baae1e
commit: f30b09b7f8aed3180d6e2f2984e32e91c7a7fcd1 [36/37] perf/core: Implement fast breakpoint modification via _IOC_MODIFY_ATTRIBUTES
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-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 f30b09b7f8aed3180d6e2f2984e32e91c7a7fcd1
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All errors (new ones prefixed by >>):
kernel/events/core.c: In function 'perf_event_modify_breakpoint':
>> kernel/events/core.c:2856:8: error: implicit declaration of function 'modify_user_hw_breakpoint_check'; did you mean 'modify_user_hw_breakpoint'? [-Werror=implicit-function-declaration]
err = modify_user_hw_breakpoint_check(bp, attr, true);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
modify_user_hw_breakpoint
cc1: some warnings being treated as errors
vim +2856 kernel/events/core.c
2848
2849 static int perf_event_modify_breakpoint(struct perf_event *bp,
2850 struct perf_event_attr *attr)
2851 {
2852 int err;
2853
2854 _perf_event_disable(bp);
2855
> 2856 err = modify_user_hw_breakpoint_check(bp, attr, true);
2857 if (err) {
2858 if (!bp->attr.disabled)
2859 _perf_event_enable(bp);
2860
2861 return err;
2862 }
2863
2864 if (!attr->disabled)
2865 _perf_event_enable(bp);
2866 return 0;
2867 }
2868
---
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: 53371 bytes --]
reply other threads:[~2018-03-13 7:29 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=201803131516.0ze2DEoS%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=chabbi.milind@gmail.com \
--cc=jolsa@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tipbuild@zytor.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
all inboxes | Powered by JetHome®