From: kbuild test robot <lkp@intel.com>
To: Kaixu Xia <xiakaixu@huawei.com>
Cc: kbuild-all@01.org, ast@plumgrid.com, davem@davemloft.net,
acme@kernel.org, mingo@redhat.com, a.p.zijlstra@chello.nl,
masami.hiramatsu.pt@hitachi.com, jolsa@kernel.org,
daniel@iogearbox.net, xiakaixu@huawei.com, wangnan0@huawei.com,
linux-kernel@vger.kernel.org, pi3orama@163.com,
hekuang@huawei.com, netdev@vger.kernel.org
Subject: [RFC PATCH] bpf: bpf_perf_event_sample_control_proto can be static
Date: Wed, 14 Oct 2015 21:49:39 +0800 [thread overview]
Message-ID: <20151014134939.GA4332@lkp-hsx03> (raw)
In-Reply-To: <1444826277-94060-2-git-send-email-xiakaixu@huawei.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
bpf_trace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
index f261333..ade24a1 100644
--- a/kernel/trace/bpf_trace.c
+++ b/kernel/trace/bpf_trace.c
@@ -236,7 +236,7 @@ static u64 bpf_perf_event_sample_control(u64 r1, u64 index, u64 flag, u64 r4, u6
return 0;
}
-const struct bpf_func_proto bpf_perf_event_sample_control_proto = {
+static const struct bpf_func_proto bpf_perf_event_sample_control_proto = {
.func = bpf_perf_event_sample_control,
.gpl_only = false,
.ret_type = RET_INTEGER,
next prev parent reply other threads:[~2015-10-14 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 12:37 [PATCH V2 0/2] bpf: enable/disable events stored in PERF_EVENT_ARRAY maps trace data output when perf sampling Kaixu Xia
2015-10-14 12:37 ` [PATCH V2 1/2] bpf: control the trace data output on current cpu " Kaixu Xia
2015-10-14 13:49 ` kbuild test robot
2015-10-14 13:49 ` kbuild test robot [this message]
2015-10-14 21:21 ` Alexei Starovoitov
2015-10-14 12:37 ` [PATCH V2 2/2] bpf: control a set of perf events by creating a new ioctl PERF_EVENT_IOC_SET_ENABLER Kaixu Xia
2015-10-14 21:28 ` Alexei Starovoitov
2015-10-15 2:21 ` xiakaixu
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=20151014134939.GA4332@lkp-hsx03 \
--to=lkp@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.com \
--cc=xiakaixu@huawei.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