From: kernel test robot <lkp@intel.com>
To: Eric DeVolder <eric.devolder@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-unstable 67/89] kernel/kexec_core.c:(.text.__crash_kexec+0x88): undefined reference to `machine_crash_shutdown'
Date: Tue, 4 Jul 2023 01:24:09 +0800 [thread overview]
Message-ID: <202307040141.Pk8IMwgE-lkp@intel.com> (raw)
Hi Eric,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: f30ee81787a5abee6c7c72b0fcc30d428319c449
commit: 1b0ee7ecbaebf3d7b9e31b529ed94f4880c495f5 [67/89] mips/kexec: refactor for kernel/Kconfig.kexec
config: mips-randconfig-r062-20230703 (https://download.01.org/0day-ci/archive/20230704/202307040141.Pk8IMwgE-lkp@intel.com/config)
compiler: mipsel-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230704/202307040141.Pk8IMwgE-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307040141.Pk8IMwgE-lkp@intel.com/
All errors (new ones prefixed by >>):
mipsel-linux-ld: kernel/kexec_core.o: in function `__crash_kexec':
>> kernel/kexec_core.c:(.text.__crash_kexec+0x88): undefined reference to `machine_crash_shutdown'
>> mipsel-linux-ld: kernel/kexec_core.c:(.text.__crash_kexec+0x90): undefined reference to `machine_kexec'
mipsel-linux-ld: kernel/kexec_core.o: in function `kernel_kexec':
>> kernel/kexec_core.c:(.text.kernel_kexec+0x98): undefined reference to `machine_shutdown'
>> mipsel-linux-ld: kernel/kexec_core.c:(.text.kernel_kexec+0xa0): undefined reference to `machine_kexec'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-03 17:24 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=202307040141.Pk8IMwgE-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=eric.devolder@oracle.com \
--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