From: kernel test robot <lkp@intel.com>
To: John Stultz <john.stultz@linaro.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Maulik Shah <mkshah@codeaurora.org>,
Stephen Boyd <swboyd@chromium.org>
Subject: [linux-next:master 998/7280] qcom-rpmh-regulator.c:undefined reference to `rpmh_write'
Date: Mon, 23 Nov 2020 10:27:51 +0800 [thread overview]
Message-ID: <202011231049.kXYmcc3E-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2478 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 95065cb54210eba86bed10cb2118041524d54573
commit: cb3659268a12602a2ad1e8e8d34ce155bb43ae6e [998/7280] soc: qcom: rpmh: Allow RPMH driver to be loaded as a module
config: arc-randconfig-r002-20201123 (attached as .config)
compiler: arc-elf-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=cb3659268a12602a2ad1e8e8d34ce155bb43ae6e
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 cb3659268a12602a2ad1e8e8d34ce155bb43ae6e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arc
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 >>):
arc-elf-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_send_request':
>> qcom-rpmh-regulator.c:(.text+0x9e): undefined reference to `rpmh_write'
>> arc-elf-ld: qcom-rpmh-regulator.c:(.text+0x9e): undefined reference to `rpmh_write'
>> arc-elf-ld: qcom-rpmh-regulator.c:(.text+0xa8): undefined reference to `rpmh_write_async'
>> arc-elf-ld: qcom-rpmh-regulator.c:(.text+0xa8): undefined reference to `rpmh_write_async'
arc-elf-ld: lib/stackdepot.o: in function `filter_irq_stacks':
stackdepot.c:(.text+0x6): undefined reference to `__irqentry_text_start'
arc-elf-ld: stackdepot.c:(.text+0x6): undefined reference to `__irqentry_text_start'
arc-elf-ld: stackdepot.c:(.text+0x26): undefined reference to `__irqentry_text_end'
arc-elf-ld: stackdepot.c:(.text+0x26): undefined reference to `__irqentry_text_end'
arc-elf-ld: stackdepot.c:(.text+0x34): undefined reference to `__softirqentry_text_start'
arc-elf-ld: stackdepot.c:(.text+0x34): undefined reference to `__softirqentry_text_start'
arc-elf-ld: stackdepot.c:(.text+0x3c): undefined reference to `__softirqentry_text_end'
arc-elf-ld: stackdepot.c:(.text+0x3c): undefined reference to `__softirqentry_text_end'
---
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: 39798 bytes --]
reply other threads:[~2020-11-23 2:28 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=202011231049.kXYmcc3E-lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=john.stultz@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=mkshah@codeaurora.org \
--cc=swboyd@chromium.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).