From: kernel test robot <lkp@intel.com>
To: Mark-PK Tsai <mark-pk.tsai@mediatek.com>,
rostedt@goodmis.org, mingo@redhat.com
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
matthias.bgg@gmail.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, mark-pk.tsai@mediatek.com,
yj.chiang@mediatek.com
Subject: Re: [PATCH] tracing: make tracer_init_tracefs initcall asynchronous
Date: Sat, 12 Mar 2022 03:12:25 +0800 [thread overview]
Message-ID: <202203120304.sJ9EJI90-lkp@intel.com> (raw)
In-Reply-To: <20220311112656.25348-1-mark-pk.tsai@mediatek.com>
Hi Mark-PK,
I love your patch! Perhaps something to improve:
[auto build test WARNING on rostedt-trace/for-next]
[also build test WARNING on v5.17-rc7 next-20220310]
[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/Mark-PK-Tsai/tracing-make-tracer_init_tracefs-initcall-asynchronous/20220311-192857
base: https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next
config: riscv-randconfig-r042-20220310 (https://download.01.org/0day-ci/archive/20220312/202203120304.sJ9EJI90-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 276ca87382b8f16a65bddac700202924228982f6)
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
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/0day-ci/linux/commit/134c5fb991a16bf28b500e8e52296447013b5b01
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Mark-PK-Tsai/tracing-make-tracer_init_tracefs-initcall-asynchronous/20220311-192857
git checkout 134c5fb991a16bf28b500e8e52296447013b5b01
# 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=riscv SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux.o(.text+0xa792a): Section mismatch in reference from the function tracefs_init() to the function .init.text:create_trace_instances()
The function tracefs_init() references
the function __init create_trace_instances().
This is often because tracefs_init lacks a __init
annotation or the annotation of create_trace_instances is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0xade5e): Section mismatch in reference from the function event_trace_init() to the function .init.text:early_event_add_tracer()
The function event_trace_init() references
the function __init early_event_add_tracer().
This is often because event_trace_init lacks a __init
annotation or the annotation of early_event_add_tracer is wrong.
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2022-03-11 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 11:26 [PATCH] tracing: make tracer_init_tracefs initcall asynchronous Mark-PK Tsai
2022-03-11 16:31 ` Steven Rostedt
2022-03-14 11:47 ` Mark-PK Tsai
2022-03-16 15:58 ` Mark-PK Tsai
2022-03-11 17:39 ` kernel test robot
2022-03-11 19:12 ` kernel test robot [this message]
2022-03-14 2:18 ` [tracing] 134c5fb991: WARNING:at_kernel/trace/trace.c:#create_trace_option_files 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=202203120304.sJ9EJI90-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=mark-pk.tsai@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yj.chiang@mediatek.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