From: kbuild test robot <lkp@intel.com>
To: yupeng0921@gmail.com
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, rostedt@goodmis.org, mingo@redhat.com,
yupeng0921@gmail.com
Subject: Re: [ftrace-bpf 1/5] add BPF_PROG_TYPE_FTRACE to bpf
Date: Wed, 15 Nov 2017 01:47:19 +0800 [thread overview]
Message-ID: <201711150015.9qmhB504%fengguang.wu@intel.com> (raw)
In-Reply-To: <1510471708-12729-1-git-send-email-yupeng0921@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.14]
[cannot apply to next-20171114]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/yupeng0921-gmail-com/add-BPF_PROG_TYPE_FTRACE-to-bpf/20171114-202535
config: parisc-allmodconfig (attached as .config)
compiler: hppa-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
# save the attached .config to linux build tree
make.cross ARCH=parisc
All errors (new ones prefixed by >>):
>> kernel/bpf/syscall.o:(.data.rel.ro+0xc): undefined reference to `ftrace_prog_ops'
---
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: 51284 bytes --]
next prev parent reply other threads:[~2017-11-14 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 7:28 yupeng0921
2017-11-12 7:28 ` [ftrace-bpf 2/5] add bpf prog interface for ftrace yupeng0921
2017-11-12 7:28 ` [ftrace-bpf 3/5] add bpf prog filter for graph trace yupeng0921
2017-11-12 7:28 ` [ftrace-bpf 4/5] enable bpf filter for graph trace in x86-64 arch yupeng0921
2017-11-12 7:28 ` [ftrace-bpf 5/5] add BPF_PROG_TYPE_FTRACE support for samples/bpf yupeng0921
2017-11-13 1:02 ` [ftrace-bpf 1/5] add BPF_PROG_TYPE_FTRACE to bpf Alexei Starovoitov
2017-11-13 8:06 ` peng yu
2017-11-17 23:48 ` Alexei Starovoitov
2017-11-14 17:47 ` kbuild test robot [this message]
2017-11-14 21:01 ` kbuild test robot
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=201711150015.9qmhB504%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yupeng0921@gmail.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®