From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [perf-tools-next:tmp.perf-tools-next 9/10] grep: tools/include/uapi/linux/fadvise.h: No such file or directory
Date: Tue, 31 Mar 2026 16:15:54 -0300 [thread overview]
Message-ID: <acwdajLKBcDiuk_I@x1> (raw)
In-Reply-To: <acu3Qeoy3pRcCrpl@rli9-mobl>
On Tue, Mar 31, 2026 at 08:00:01PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git tmp.perf-tools-next
> head: 02288074fcf09dec98dcb3fefdada4ebb4a91d33
> commit: 7eb9876f1d9fdb6f6a8ed5737452178ca2169205 [9/10] perf beauty: Move copy of fadvise.h from tools/include/ to tools/perf/trace/beauty/include/
> config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260331/202603311011.IoMYrQLJ-lkp@intel.com/config)
> compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260331/202603311011.IoMYrQLJ-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/r/202603311011.IoMYrQLJ-lkp@intel.com/
Since this hasn't touched a non-tmp branch, I'll not add it, i.e. its a
v2.
Thanks anyway, I found and fixed the issue,
- Arnaldo
> All errors (new ones prefixed by >>):
>
> Makefile.config:576: No elfutils/debuginfod.h found, no debuginfo server support, please install libdebuginfod-dev/elfutils-debuginfod-client-devel or equivalent
> Makefile.config:963: No libllvm 13+ found, slower source file resolution, please install llvm-devel/llvm-dev
> Makefile.config:1159: Rust is not found. Test workloads with rust are disabled.
> >> grep: tools/include/uapi/linux/fadvise.h: No such file or directory
> PERF_VERSION = 7.0.rc4.g7eb9876f1d9f
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-31 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 12:00 [perf-tools-next:tmp.perf-tools-next 9/10] grep: tools/include/uapi/linux/fadvise.h: No such file or directory kernel test robot
2026-03-31 19:15 ` Arnaldo Carvalho de Melo [this message]
2026-03-31 20:25 ` Namhyung Kim
2026-03-31 20:48 ` Arnaldo Carvalho de Melo
2026-03-31 20:58 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2026-03-31 8:46 kernel 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=acwdajLKBcDiuk_I@x1 \
--to=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=namhyung@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.