[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56BB95C3.8010003@zytor.com>
Date: Wed, 10 Feb 2016 11:55:47 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
kbuild test robot <fengguang.wu@...el.com>
Cc: Johannes Weiner <hannes@...xchg.org>, kbuild-all@...org,
linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
Linux Memory Management List <linux-mm@...ck.org>,
Matt Fleming <matt@...eblueprint.co.uk>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: undefined reference to `efi_call'
On 02/10/16 11:52, Andrew Morton wrote:
> On Wed, 10 Feb 2016 16:48:28 +0800 kbuild test robot <fengguang.wu@...el.com> wrote:
>
>> 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'
>
> I'd be surprised if the above patch caused this.
>
> CONFIG_EFI=n
>
> CONFIG_X86_UV does not depend on EFI.
>
X86_UV ought to depend on EFI.
-hpa
Powered by blists - more mailing lists