From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Feiyang Chen <chris.chenfeiyang@gmail.com>
Cc: Feiyang Chen <chenfeiyang@loongson.cn>,
chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
tangyouling@loongson.cn, linux-mips@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: Fix build error for loongson64 and sgi-ip27
Date: Thu, 24 Mar 2022 09:51:21 +0100 [thread overview]
Message-ID: <20220324085121.GA5250@alpha.franken.de> (raw)
In-Reply-To: <78559205988aa1c0b42ee6ac20bb0fec3200f978.1647682458.git.chenfeiyang@loongson.cn>
On Sat, Mar 19, 2022 at 05:40:02PM +0800, Feiyang Chen wrote:
> Select HAVE_ARCH_NODEDATA_EXTENSION for loongson64 to fix build error
> when CONFIG_NUMA=y:
>
> mips64el-unknown-linux-gnu-ld: mm/page_alloc.o: in function `free_area_init':
> (.init.text+0x1714): undefined reference to `node_data'
> mips64el-unknown-linux-gnu-ld: (.init.text+0x1730): undefined reference to `node_data'
>
> Also, select HAVE_ARCH_NODEDATA_EXTENSION for sgi-ip27 to fix build error:
>
> mips64el-unknown-linux-gnu-ld: mm/page_alloc.o: in function `free_area_init':
> page_alloc.c:(.init.text+0x1ba8): undefined reference to `node_data'
> mips64el-unknown-linux-gnu-ld: page_alloc.c:(.init.text+0x1bcc): undefined reference to `node_data'
> mips64el-unknown-linux-gnu-ld: page_alloc.c:(.init.text+0x1be4): undefined reference to `node_data'
> mips64el-unknown-linux-gnu-ld: page_alloc.c:(.init.text+0x1bf4): undefined reference to `node_data'
>
> Signed-off-by: Feiyang Chen <chenfeiyang@loongson.cn>
> ---
> arch/mips/Kconfig | 5 +++++
> arch/mips/loongson64/numa.c | 10 ++++++++++
> arch/mips/sgi-ip27/ip27-memory.c | 10 ++++++++++
> 3 files changed, 25 insertions(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-03-24 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 9:40 [PATCH v2] MIPS: Fix build error for loongson64 and sgi-ip27 Feiyang Chen
2022-03-19 13:12 ` Huacai Chen
2022-03-24 8:51 ` Thomas Bogendoerfer [this message]
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=20220324085121.GA5250@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=chris.chenfeiyang@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=tangyouling@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).