From: kbuild test robot <lkp@intel.com>
To: "Andrew, Morton," <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org, Johannes Weiner <hannes@cmpxchg.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [feng:linux-mm 452/660] vexpress-poweroff.c:undefined reference to `devm_regmap_init_vexpress_config'
Date: Tue, 2 Jun 2020 02:38:55 +0800 [thread overview]
Message-ID: <202006020250.O19KDPjL%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Hi Andrew,
It's probably a bug fix that unveils the link errors.
tree: feng/linux-mm
head: 650a37b8fc9316c2e910099058345db7591708f9
commit: c15130ebef2f485bf34b42d78b7a6f4aad621bd3 [452/660] linux-next-rejects
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-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
git checkout c15130ebef2f485bf34b42d78b7a6f4aad621bd3
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
aarch64-linux-ld: drivers/power/reset/vexpress-poweroff.o: in function `vexpress_reset_probe':
>> vexpress-poweroff.c:(.text+0x470): undefined reference to `devm_regmap_init_vexpress_config'
---
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: 72553 bytes --]
reply other threads:[~2020-06-01 18:39 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=202006020250.O19KDPjL%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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).