From: kbuild test robot <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Michal Hocko <mhocko@kernel.org>
Subject: [linux-next:master 6909/7874] undefined reference to `early_panic'
Date: Wed, 23 Dec 2015 01:43:56 +0800 [thread overview]
Message-ID: <201512230154.Qb1INcNC%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
Hi Andrew,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3248efff60b83f93dad704e98d80657285aa0780
commit: bbbfaae3a26dd9762187f0daac74889661a4f0dd [6909/7874] mm-oom-introduce-oom-reaper-fix-fix-2
config: tile-allnoconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout bbbfaae3a26dd9762187f0daac74889661a4f0dd
# save the attached .config to linux build tree
make.cross ARCH=tile
All errors (new ones prefixed by >>):
arch/tile/built-in.o: In function `setup_arch':
>> (.init.text+0x15d8): undefined reference to `early_panic'
arch/tile/built-in.o: In function `setup_arch':
(.init.text+0x1610): undefined reference to `early_panic'
arch/tile/built-in.o: In function `setup_arch':
(.init.text+0x1800): undefined reference to `early_panic'
arch/tile/built-in.o: In function `setup_arch':
(.init.text+0x1828): undefined reference to `early_panic'
arch/tile/built-in.o: In function `setup_arch':
(.init.text+0x1bd8): undefined reference to `early_panic'
arch/tile/built-in.o:(.init.text+0x1c18): more undefined references to `early_panic' follow
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 3974 bytes --]
reply other threads:[~2015-12-22 17:44 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=201512230154.Qb1INcNC%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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