From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [linux-next:master] BUILD REGRESSION d01f2f7e35573049673b71e18be7abfe3f80323f
Date: Fri, 26 Feb 2021 11:13:36 -0800 [thread overview]
Message-ID: <20210226111336.91a89c0f5230eae69196f71e@linux-foundation.org> (raw)
In-Reply-To: <6039178e.nIA6K0eHFcbkwcNB%lkp@intel.com>
On Fri, 26 Feb 2021 23:45:18 +0800 kernel test robot <lkp@intel.com> wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: d01f2f7e35573049673b71e18be7abfe3f80323f Add linux-next specific files for 20210226
>
> ...
>
> page_alloc.c:(.text+0xe028): undefined reference to `node_reclaim_distance'
> riscv32-linux-ld: page_alloc.c:(.text+0xe02c): undefined reference to `node_reclaim_distance'
>
> ...
>
> |-- riscv-randconfig-p001-20210226
> | |-- page_alloc.c:(.text):undefined-reference-to-node_reclaim_distance
> | `-- riscv32-linux-ld:page_alloc.c:(.text):undefined-reference-to-node_reclaim_distance
I assume the riscv randconfig managed to create a .config with
CONFIG_NUMA=n, CONFIG_SMP=y. Configuration doesn't make a lot of
sense, unless someone has a single-CPU machine with cpuless nodes...
Could the riscv maintainers please test and merge this?
--- a/arch/riscv/Kconfig~a
+++ a/arch/riscv/Kconfig
@@ -314,6 +314,7 @@ endchoice
# Common NUMA Features
config NUMA
bool "NUMA Memory Allocation and Scheduler Support"
+ depends on SMP
select GENERIC_ARCH_NUMA
select OF_NUMA
select ARCH_SUPPORTS_NUMA_BALANCING
_
next prev parent reply other threads:[~2021-02-26 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 15:45 kernel test robot
2021-02-26 19:13 ` Andrew Morton [this message]
2021-02-26 19:43 ` Atish Patra
2021-02-26 20:26 ` Palmer Dabbelt
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=20210226111336.91a89c0f5230eae69196f71e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/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
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