LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org, mhocko@suse.cz,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
	Ravikiran Thirumalai <kiran@scalemp.com>,
	Shai Fultheim <shai@scalemp.com>, X86 ML <x86@kernel.org>
Subject: Re: mmotm 2018-10-30-16-08 uploaded (arch/x86/kernel/vsmp_64.c)
Date: Tue, 30 Oct 2018 20:20:09 -0700	[thread overview]
Message-ID: <9e14d183-55a4-8299-7a18-0404e50bf004@infradead.org> (raw)
In-Reply-To: <20181030230905.xHZmM%akpm@linux-foundation.org>

On 10/30/18 4:09 PM, akpm@linux-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

  reply	other threads:[~2018-10-31  3:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 23:09 mmotm 2018-10-30-16-08 uploaded akpm
2018-10-31  3:20 ` Randy Dunlap [this message]
2018-11-01  9:36   ` [PATCH] x86/build: Build VSMP support only if selected Thomas Gleixner
2018-11-01 10:39     ` Shai Fultheim (Shai@ScaleMP.com)
2018-11-01 13:10       ` Eial Czerwacki
2018-11-01 13:17         ` Thomas Gleixner
2018-11-01 13:45         ` Juergen Gross
2018-11-01 15:09           ` Eial Czerwacki
2018-11-01 15:39             ` Juergen Gross

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=9e14d183-55a4-8299-7a18-0404e50bf004@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=kiran@scalemp.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shai@scalemp.com \
    --cc=x86@kernel.org \
    --subject='Re: mmotm 2018-10-30-16-08 uploaded (arch/x86/kernel/vsmp_64.c)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).