From: Mike Qiu <qiudayu@linux.vnet.ibm.com>
To: Mike Qiu <qiudayu@linux.vnet.ibm.com>
Cc: sfr@canb.auug.org.au, jlarrew@linux.vnet.ibm.com,
paulus@samba.org, srivatsa.bhat@linux.vnet.ibm.com,
alistair@popple.id.au, nfont@linux.vnet.ibm.com,
akpm@linux-foundation.org, rcj@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/mm: Fix ".__node_distance" undefined
Date: Thu, 17 Apr 2014 11:10:16 +0800 [thread overview]
Message-ID: <534F4618.6080405@linux.vnet.ibm.com> (raw)
In-Reply-To: <1397570417-1714-1-git-send-email-qiudayu@linux.vnet.ibm.com>
Any update about this patch ?
Thanks
Mike
On 04/15/2014 10:00 PM, Mike Qiu wrote:
> CHK include/config/kernel.release
> CHK include/generated/uapi/linux/version.h
> CHK include/generated/utsrelease.h
> ...
> Building modules, stage 2.
> WARNING: 1 bad relocations
> c0000000013d6a30 R_PPC64_ADDR64 uprobes_fetch_type_table
> WRAP arch/powerpc/boot/zImage.pseries
> WRAP arch/powerpc/boot/zImage.epapr
> MODPOST 1849 modules
> ERROR: ".__node_distance" [drivers/block/nvme.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> make: *** Waiting for unfinished jobs....
>
> The reason is symbol "__node_distance" not been exported in powerpc.
>
> Signed-off-by: Mike Qiu <qiudayu@linux.vnet.ibm.com>
> ---
> arch/powerpc/mm/numa.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
> index 4ebbb9e..3b181b2 100644
> --- a/arch/powerpc/mm/numa.c
> +++ b/arch/powerpc/mm/numa.c
> @@ -232,6 +232,7 @@ int __node_distance(int a, int b)
>
> return distance;
> }
> +EXPORT_SYMBOL(__node_distance);
>
> static void initialize_distance_lookup_table(int nid,
> const __be32 *associativity)
prev parent reply other threads:[~2014-04-17 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 14:00 [PATCH] powerpc/mm: Fix ".__node_distance" undefined Mike Qiu
2014-04-17 3:10 ` Mike Qiu [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=534F4618.6080405@linux.vnet.ibm.com \
--to=qiudayu@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alistair@popple.id.au \
--cc=jlarrew@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=rcj@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=srivatsa.bhat@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).