From: kernel test robot <lkp@intel.com>
To: Michal Suchanek <msuchanek@suse.de>, bpf@vger.kernel.org
Cc: kbuild-all@lists.01.org, Michal Suchanek <msuchanek@suse.de>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>
Subject: Re: [PATCH] libbpf: Remove from kernel tree.
Date: Mon, 19 Jul 2021 03:31:13 +0800 [thread overview]
Message-ID: <202107190321.6lABVeQC-lkp@intel.com> (raw)
In-Reply-To: <20210718065039.15627-1-msuchanek@suse.de>
[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]
Hi Michal,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf/master]
[also build test ERROR on linus/master next-20210716]
[cannot apply to bpf-next/master sparc-next/master v5.14-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Michal-Suchanek/libbpf-Remove-from-kernel-tree/20210718-145456
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
config: i386-randconfig-a001-20210718 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/2ea8ab79c2a463d1811eca90527b055e1763decd
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Michal-Suchanek/libbpf-Remove-from-kernel-tree/20210718-145456
git checkout 2ea8ab79c2a463d1811eca90527b055e1763decd
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> kernel/bpf/preload/iterators/iterators.c:10:10: fatal error: bpf/libbpf.h: No such file or directory
10 | #include <bpf/libbpf.h>
| ^~~~~~~~~~~~~~
compilation terminated.
vim +10 kernel/bpf/preload/iterators/iterators.c
d71fa5c9763c24 Alexei Starovoitov 2020-08-18 @10 #include <bpf/libbpf.h>
d71fa5c9763c24 Alexei Starovoitov 2020-08-18 11 #include <bpf/bpf.h>
d71fa5c9763c24 Alexei Starovoitov 2020-08-18 12 #include <sys/mount.h>
d71fa5c9763c24 Alexei Starovoitov 2020-08-18 13 #include "iterators.skel.h"
d71fa5c9763c24 Alexei Starovoitov 2020-08-18 14 #include "bpf_preload_common.h"
d71fa5c9763c24 Alexei Starovoitov 2020-08-18 15
---
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: 32529 bytes --]
prev parent reply other threads:[~2021-07-18 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210718065039.15627-1-msuchanek@suse.de>
2021-07-18 19:04 ` [PATCH] libbpf: Remove from kernel tree Daniel Borkmann
2021-07-18 19:36 ` Michal Suchánek
2021-07-18 21:54 ` Andrii Nakryiko
2021-07-18 21:55 ` Andrii Nakryiko
2021-07-18 19:31 ` kernel test robot [this message]
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=202107190321.6lABVeQC-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kbuild-all@lists.01.org \
--cc=kpsingh@kernel.org \
--cc=msuchanek@suse.de \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).