Re: [perf-tools-next:tmp.perf-tools-next 9/10] grep: tools/include/uapi/linux/fadvise.h: No such file or directory

Arnaldo Carvalho de Melo
2026-03-31T20:58:42Z

On Tue, Mar 31, 2026 at 05:48:28PM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Mar 31, 2026 at 01:25:04PM -0700, Namhyung Kim wrote:
> > Hi Arnaldo,
> >
> > On Tue, Mar 31, 2026 at 04:15:54PM -0300, Arnaldo Carvalho de Melo wrote:
> > > 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,
> >
> > Do you want to add it to perf-tools or send v2? I thought you wanted to
> > have it in perf-tools-next as you added "next" in the patch subject.
>
> v2, yeah, for next.
>
> Will send now, together with the other related patch, so that sashiko
> can test the series and not fail to test the the fadvise one, that
> depends on the first.

Got your point, it is in perf-tools-next/tmp.perf-tools-next already, so
you'll need to replace what is there with what I'll send as v2, since it
didn't hit perf-tools-next/perf-tools-next.

Ok, sending it now.

- Arnaldo