From: kernel test robot <lkp@intel.com>
To: Alex Sverdlin <alexander.sverdlin@nokia.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Subject: [linux-next:master 6218/7700] arch/arm/kernel/module-plts.c:26:2: error: 'FTRACE_ADDR' undeclared here (not in a function)
Date: Tue, 8 Jun 2021 14:29:04 +0800 [thread overview]
Message-ID: <202106081458.USmfavfo-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 7f09e895a7f3e0af63bf9ec6c7c22893ec7e6c8e
commit: 1f12fb25c5c5d22fce1378f61f6c8a7e981eaf99 [6218/7700] ARM: 9079/1: ftrace: Add MODULE_PLTS support
config: arm-randconfig-c004-20210607 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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=1f12fb25c5c5d22fce1378f61f6c8a7e981eaf99
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 1f12fb25c5c5d22fce1378f61f6c8a7e981eaf99
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> arch/arm/kernel/module-plts.c:26:2: error: 'FTRACE_ADDR' undeclared here (not in a function)
26 | FTRACE_ADDR,
| ^~~~~~~~~~~
vim +/FTRACE_ADDR +26 arch/arm/kernel/module-plts.c
23
24 static const u32 fixed_plts[] = {
25 #ifdef CONFIG_FUNCTION_TRACER
> 26 FTRACE_ADDR,
27 MCOUNT_ADDR,
28 #endif
29 };
30
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35141 bytes --]
reply other threads:[~2021-06-08 6:30 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=202106081458.USmfavfo-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.sverdlin@nokia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=rmk+kernel@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).