From: kbuild test robot <fengguang.wu@intel.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: undefined reference to `efi_call'
Date: Wed, 10 Feb 2016 16:48:28 +0800 [thread overview]
Message-ID: <201602101626.jtqGm2RN%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
Hi Johannes,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2178cbc68f3602dc0b5949b9be2c8383ad3d93ef
commit: 489c2a20a414351fe0813a727c34600c0f7292ae mm: memcontrol: introduce CONFIG_MEMCG_LEGACY_KMEM
date: 3 weeks ago
config: x86_64-randconfig-s3-02101458 (attached as .config)
reproduce:
git checkout 489c2a20a414351fe0813a727c34600c0f7292ae
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/built-in.o: In function `uv_bios_call':
>> (.text+0xeba00): undefined reference to `efi_call'
---
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: 23241 bytes --]
next reply other threads:[~2016-02-10 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 8:48 kbuild test robot [this message]
2016-02-10 19:52 ` Andrew Morton
2016-02-10 19:55 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2016-01-26 10:29 kbuild test robot
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=201602101626.jtqGm2RN%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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