From: kernel test robot <lkp@intel.com>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>
Subject: [linux-next:master 14283/14376] trace.c:undefined reference to `ftrace_stub_direct_tramp'
Date: Sat, 29 Apr 2023 13:12:34 +0800 [thread overview]
Message-ID: <202304291308.YpmrjzVV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 92e815cf07ed24ee1c51b122f24ffcf2964b4b13
commit: e287501e00c6e935a6e182f6992f97ee181788d3 [14283/14376] Merge branch 'loongarch-next' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20230429/202304291308.YpmrjzVV-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.1.0
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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e287501e00c6e935a6e182f6992f97ee181788d3
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout e287501e00c6e935a6e182f6992f97ee181788d3
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304291308.YpmrjzVV-lkp@intel.com/
All errors (new ones prefixed by >>):
loongarch64-linux-ld: kernel/trace/trace.o: in function `.L3177':
>> trace.c:(.init.text+0x16e4): undefined reference to `ftrace_stub_direct_tramp'
>> loongarch64-linux-ld: trace.c:(.init.text+0x16e8): undefined reference to `ftrace_stub_direct_tramp'
>> loongarch64-linux-ld: trace.c:(.init.text+0x16e8): undefined reference to `ftrace_stub_direct_tramp'
loongarch64-linux-ld: kernel/trace/trace.o: in function `.L3180':
trace.c:(.init.text+0x17bc): undefined reference to `ftrace_stub_direct_tramp'
loongarch64-linux-ld: trace.c:(.init.text+0x17c0): undefined reference to `ftrace_stub_direct_tramp'
loongarch64-linux-ld: kernel/trace/trace.o:trace.c:(.init.text+0x17c0): more undefined references to `ftrace_stub_direct_tramp' follow
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-29 5:13 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 \
--in-reply-to=202304291308.YpmrjzVV-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=linux-mm@kvack.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