From: kernel test robot <lkp@intel.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: undefined reference to `cpu_sa110_suspend_size'
Date: Mon, 14 Mar 2022 10:29:34 +0800 [thread overview]
Message-ID: <202203141021.N78GB4Ux-lkp@intel.com> (raw)
Hi Dmitry,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 09688c0166e76ce2fb85e86b9d99be8b0084cdf9
commit: faae6c9f2e68e62687636a7d6e0517b3bf594add cpuidle: tegra: Enable compile testing
date: 5 months ago
config: arm-randconfig-r023-20220314 (https://download.01.org/0day-ci/archive/20220314/202203141021.N78GB4Ux-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.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/torvalds/linux.git/commit/?id=faae6c9f2e68e62687636a7d6e0517b3bf594add
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout faae6c9f2e68e62687636a7d6e0517b3bf594add
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
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 >>):
arm-linux-gnueabi-ld: arch/arm/kernel/sleep.o: in function `__cpu_suspend':
>> (.text+0x68): undefined reference to `cpu_sa110_suspend_size'
arm-linux-gnueabi-ld: arch/arm/kernel/suspend.o: in function `__cpu_suspend_save':
>> suspend.c:(.text+0x154): undefined reference to `cpu_sa110_do_suspend'
>> arm-linux-gnueabi-ld: suspend.c:(.text+0x17c): undefined reference to `cpu_sa110_do_resume'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for ARM_CPU_SUSPEND
Depends on ARCH_SUSPEND_POSSIBLE
Selected by
- ARM_TEGRA_CPUIDLE && CPU_IDLE && (ARM || ARM64) && (ARCH_TEGRA || COMPILE_TEST && !ARM64 && MMU
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-03-14 2:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 2:29 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-08 8:45 undefined reference to `cpu_sa110_suspend_size' kernel test robot
2022-01-24 12:47 kernel test robot
2022-01-24 12:47 ` kernel test robot
2021-12-14 20:39 kernel test robot
2021-12-14 20:39 ` kernel test robot
2021-05-25 0:59 kernel test robot
2021-05-25 0:59 ` kernel test robot
2021-03-02 4:54 kernel test robot
2021-03-02 4:54 ` kernel test robot
2021-01-24 9:41 kernel test robot
2021-01-24 9:41 ` kernel test robot
2020-12-07 4:46 kernel test robot
2020-12-07 4:46 ` kernel test robot
2020-12-11 2:58 ` Randy Dunlap
2020-12-11 2:58 ` Randy Dunlap
2020-11-24 20:58 kernel test robot
2020-11-24 20:58 ` kernel test robot
2020-11-11 11:57 kernel test robot
2020-11-11 11:57 ` kernel test robot
2020-11-24 0:32 ` Randy Dunlap
2020-11-24 0:32 ` Randy Dunlap
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=202203141021.N78GB4Ux-lkp@intel.com \
--to=lkp@intel.com \
--cc=digetx@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.