From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Morton <akpm@linux-foundation.org>,
kbuild test robot <fengguang.wu@intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Linux Memory Management List <linux-mm@kvack.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: undefined reference to `efi_call'
Date: Wed, 10 Feb 2016 11:55:47 -0800 [thread overview]
Message-ID: <56BB95C3.8010003@zytor.com> (raw)
In-Reply-To: <20160210115234.234e2bab71db2028c98b58ad@linux-foundation.org>
On 02/10/16 11:52, Andrew Morton wrote:
> On Wed, 10 Feb 2016 16:48:28 +0800 kbuild test robot <fengguang.wu@intel.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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Morton <akpm@linux-foundation.org>,
kbuild test robot <fengguang.wu@intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Linux Memory Management List <linux-mm@kvack.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: undefined reference to `efi_call'
Date: Wed, 10 Feb 2016 11:55:47 -0800 [thread overview]
Message-ID: <56BB95C3.8010003@zytor.com> (raw)
In-Reply-To: <20160210115234.234e2bab71db2028c98b58ad@linux-foundation.org>
On 02/10/16 11:52, Andrew Morton wrote:
> On Wed, 10 Feb 2016 16:48:28 +0800 kbuild test robot <fengguang.wu@intel.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
next prev parent reply other threads:[~2016-02-10 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 8:48 undefined reference to `efi_call' kbuild test robot
2016-02-10 19:52 ` Andrew Morton
2016-02-10 19:52 ` Andrew Morton
2016-02-10 19:55 ` H. Peter Anvin [this message]
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=56BB95C3.8010003@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.