From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev, 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 17:48:25 -0300 [thread overview]
Message-ID: <acwzGca2RX1dEILf@x1> (raw)
In-Reply-To: <acwtoHaXuv-MlgTz@google.com>
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.
- Arnaldo
next prev parent reply other threads:[~2026-03-31 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <acu3Qeoy3pRcCrpl@rli9-mobl>
2026-03-31 19:15 ` [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-31 20:25 ` Namhyung Kim
2026-03-31 20:48 ` Arnaldo Carvalho de Melo [this message]
2026-03-31 20:58 ` Arnaldo Carvalho de Melo
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=acwzGca2RX1dEILf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox