From: kernel test robot <[email protected]>
To: "Steven Rostedt (Google)" <[email protected]>
Cc: [email protected], [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:rostedt/linux-trace/ftrace/core 1/5] include/trace/trace_custom_events.h:38:10: fatal error: 'stages/stage1_defines.h' file not found
Date: Thu, 31 Mar 2022 06:22:58 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block rostedt/linux-trace/ftrace/core
head: 025833e54d2b7b031c44642a14df39a67a524b9a
commit: 7ebdde13050a7d880ef7403fd10c30f5167b6f0b [1/5] tracing: Rename the staging files for trace_events
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220331/[email protected]/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 0f6d9501cf49ce02937099350d08f20c4af86f3d)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/ammarfaizi2/linux-block/commit/7ebdde13050a7d880ef7403fd10c30f5167b6f0b
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block rostedt/linux-trace/ftrace/core
git checkout 7ebdde13050a7d880ef7403fd10c30f5167b6f0b
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash samples/trace_events/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>
All errors (new ones prefixed by >>):
In file included from samples/trace_events/trace_custom_sched.c:24:
In file included from samples/trace_events/./trace_custom_sched.h:96:
In file included from include/trace/define_custom_trace.h:55:
>> include/trace/trace_custom_events.h:38:10: fatal error: 'stages/stage1_defines.h' file not found
#include "stages/stage1_defines.h"
^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +38 include/trace/trace_custom_events.h
3a73333fb370f7 Steven Rostedt (Google 2022-03-03 37)
3a73333fb370f7 Steven Rostedt (Google 2022-03-03 @38) #include "stages/stage1_defines.h"
3a73333fb370f7 Steven Rostedt (Google 2022-03-03 39)
:::::: The code at line 38 was first introduced by commit
:::::: 3a73333fb370f7b65de9d94c53df503642bda789 tracing: Add TRACE_CUSTOM_EVENT() macro
:::::: TO: Steven Rostedt (Google) <[email protected]>
:::::: CC: Steven Rostedt (Google) <[email protected]>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-03-30 22:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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