[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e14d183-55a4-8299-7a18-0404e50bf004@infradead.org>
Date: Tue, 30 Oct 2018 20:20:09 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: akpm@...ux-foundation.org, broonie@...nel.org, mhocko@...e.cz,
sfr@...b.auug.org.au, linux-next@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org,
Ravikiran Thirumalai <kiran@...lemp.com>,
Shai Fultheim <shai@...lemp.com>, X86 ML <x86@...nel.org>
Subject: Re: mmotm 2018-10-30-16-08 uploaded (arch/x86/kernel/vsmp_64.c)
On 10/30/18 4:09 PM, akpm@...ux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-10-30-16-08 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
Build error on x86_64 from origin.patch (i.e., not mmotm)
when CONFIG_PCI is not enabled:
Oh: CONFIG_X86_VSMP is also not enabled, but
arch/x86/kernel/Makefile always tries to build vsmp_64.o.
ld: arch/x86/kernel/vsmp_64.o: in function `vsmp_cap_cpus':
vsmp_64.c:(.init.text+0x1e): undefined reference to `read_pci_config'
--
~Randy
Powered by blists - more mailing lists