From: kbuild test robot <lkp@intel.com>
To: Fangrui Song <maskray@google.com>
Cc: kbuild-all@lists.01.org, bpf@vger.kernel.org,
netdev@vger.kernel.org, daniel@iogearbox.net,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
clang-built-linux@googlegroups.com,
Stanislav Fomichev <sdf@google.com>,
davem@davemloft.net, ast@kernel.org
Subject: Re: [PATCH bpf] bpf: Support llvm-objcopy and llvm-objdump for vmlinux BTF
Date: Wed, 18 Mar 2020 02:34:03 +0800 [thread overview]
Message-ID: <202003180233.P2XlAZ3C%lkp@intel.com> (raw)
In-Reply-To: <20200317011654.zkx5r7so53skowlc@google.com>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
Hi Fangrui,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf/master]
[also build test WARNING on net/master linus/master v5.6-rc6]
[cannot apply to net-next/master next-20200317]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Fangrui-Song/bpf-Support-llvm-objcopy-and-llvm-objdump-for-vmlinux-BTF/20200317-125132
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
config: i386-randconfig-g003-20200317 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> objcopy: .tmp_vmlinux.btf: warning: empty loadable segment detected at vaddr=0xc1000000, is this intentional?
objcopy: .tmp_vmlinux.btf: warning: empty loadable segment detected at vaddr=0xc1aae000, is this intentional?
1+0 records in
1+0 records out
1 byte copied, 8.22e-05 s, 12.2 kB/s
---
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: 33334 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH bpf] bpf: Support llvm-objcopy and llvm-objdump for vmlinux BTF
Date: Wed, 18 Mar 2020 02:34:03 +0800 [thread overview]
Message-ID: <202003180233.P2XlAZ3C%lkp@intel.com> (raw)
In-Reply-To: <20200317011654.zkx5r7so53skowlc@google.com>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
Hi Fangrui,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf/master]
[also build test WARNING on net/master linus/master v5.6-rc6]
[cannot apply to net-next/master next-20200317]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Fangrui-Song/bpf-Support-llvm-objcopy-and-llvm-objdump-for-vmlinux-BTF/20200317-125132
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
config: i386-randconfig-g003-20200317 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> objcopy: .tmp_vmlinux.btf: warning: empty loadable segment detected at vaddr=0xc1000000, is this intentional?
objcopy: .tmp_vmlinux.btf: warning: empty loadable segment detected at vaddr=0xc1aae000, is this intentional?
1+0 records in
1+0 records out
1 byte copied, 8.22e-05 s, 12.2 kB/s
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 33334 bytes --]
next prev parent reply other threads:[~2020-03-17 18:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 1:16 [PATCH bpf] bpf: Support llvm-objcopy and llvm-objdump for vmlinux BTF Fangrui Song
2020-03-17 3:10 ` Andrii Nakryiko
2020-03-17 3:37 ` [PATCH bpf v2] " Fangrui Song
2020-03-17 5:09 ` Andrii Nakryiko
2020-03-17 5:21 ` Fangrui Song
2020-03-17 5:31 ` Andrii Nakryiko
2020-03-17 5:43 ` [PATCH bpf v3] " Fangrui Song
2020-03-17 16:05 ` Stanislav Fomichev
2020-03-17 16:24 ` Stanislav Fomichev
2020-03-17 20:58 ` [PATCH bpf-next v4] " Fangrui Song
2020-03-17 23:37 ` Andrii Nakryiko
2020-03-18 17:59 ` Fangrui Song
2020-03-18 18:30 ` Andrii Nakryiko
2020-03-18 18:53 ` Fangrui Song
2020-03-18 19:23 ` Andrii Nakryiko
2020-03-17 17:02 ` [PATCH bpf] " kbuild test robot
2020-03-17 17:02 ` kbuild test robot
2020-03-17 18:34 ` kbuild test robot [this message]
2020-03-17 18:34 ` 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=202003180233.P2XlAZ3C%lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kbuild-all@lists.01.org \
--cc=maskray@google.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.