From: Randy Dunlap <rdunlap@xenotime•net>
To: Borislav Petkov <bp@amd64•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
linux-edac@vger•kernel.org
Subject: Re: linux-next: Tree for Feb 1 (mce_amd.c)
Date: Thu, 02 Feb 2012 09:53:03 -0800 [thread overview]
Message-ID: <4F2ACD7F.2020506@xenotime.net> (raw)
In-Reply-To: <20120202142628.GA1052@aftab>
On 02/02/2012 06:26 AM, Borislav Petkov wrote:
> On Wed, Feb 01, 2012 at 10:54:36AM -0800, Randy Dunlap wrote:
>> On 01/31/2012 10:16 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120131:
>>
>>
>> mce_amd.c:(.cpuinit.text+0x4723): undefined reference to `cpu_llc_shared_map'
>
> Yeah, -rc2 has that problem too with your randconfig. The issue is with
> CONFIG_SMP not being set.
>
> The following chunk should cure it:
Acked-by: Randy Dunlap <rdunlap@xenotime•net>
Thanks.
> --
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 5bed94e..63fcb8a 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -897,7 +897,7 @@ config X86_MCE_INTEL
> config X86_MCE_AMD
> def_bool y
> prompt "AMD MCE features"
> - depends on X86_MCE && X86_LOCAL_APIC
> + depends on X86_MCE && X86_LOCAL_APIC && SMP
> ---help---
> Additional support for AMD specific MCE features such as
> the DRAM Error Threshold.
> --
>
> Thanks.
>
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2012-02-02 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:16 linux-next: Tree for Feb 1 Stephen Rothwell
2012-02-01 18:51 ` linux-next: Tree for Feb 1 (media/dvb/dm1105) Randy Dunlap
2012-02-01 18:54 ` linux-next: Tree for Feb 1 (mce_amd.c) Randy Dunlap
2012-02-02 14:26 ` Borislav Petkov
2012-02-02 17:53 ` Randy Dunlap [this message]
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=4F2ACD7F.2020506@xenotime.net \
--to=rdunlap@xenotime$(echo .)net \
--cc=bp@amd64$(echo .)org \
--cc=linux-edac@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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