[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F0CA652.5040103@xenotime.net>
Date: Tue, 10 Jan 2012 12:57:54 -0800
From: Randy Dunlap <rdunlap@...otime.net>
To: Bjorn Helgaas <bhelgaas@...gle.com>
CC: Jesse Barnes <jbarnes@...tuousgeek.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
x86 maintainers <x86@...nel.org>, linux-pci@...r.kernel.org,
Yinghai Lu <yinghai@...nel.org>
Subject: Re: linux-next: Tree for Jan 9 (arch/x86/pci/amd_bus.c)
On 01/09/2012 02:40 PM, Bjorn Helgaas wrote:
> On Mon, Jan 9, 2012 at 2:05 PM, Randy Dunlap <rdunlap@...otime.net> wrote:
>> on several i386 builds:
>>
>> amd_bus.c:(.init.text+0x134b): undefined reference to `amd_get_mmconfig_range'
>
> This is my fault. I moved some code from amd_bus.c to amd_nb.c, and builds with
>
> CONFIG_PCI=y
> # CONFIG_AMD_NB not set
>
> now fail. The attached patch should fix it. I'll repost the series
> ("x86/PCI: amd: factor out MMCONFIG discovery") with the fix.
>
> Yinghai, it looks to me like there's no reason to build amd_bus.o
> unless we have CONFIG_AMD_NB=y, but speak up if I'm wrong :)
Seems to work for me. Thanks.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists