On 01/09/2012 02:40 PM, Bjorn Helgaas wrote:
> On Mon, Jan 9, 2012 at 2:05 PM, Randy Dunlap <rdunlap@xxxxxxxxxxxx> 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-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
