From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: kernel: compiling issue, need 'EXPORT_SYMBOL(clear_page)'
Date: Mon, 20 May 2013 15:15:08 +0800 [thread overview]
Message-ID: <5199CD7C.4080304@asianux.com> (raw)
In-Reply-To: <5199CCF9.4030305@asianux.com>
After this patch, can pass building arm64 with allmodconfig under
next-20130517 tree. :-)
On 05/20/2013 03:12 PM, Chen Gang wrote:
>
> Need 'EXPORT_SYMBOL(clear_page)' if building with allmodconfig.
>
> The related errors:
> ERROR: "clear_page" [fs/ocfs2/dlm/ocfs2_dlm.ko] undefined!
> ERROR: "clear_page" [fs/ntfs/ntfs.ko] undefined!
> ERROR: "clear_page" [fs/gfs2/gfs2.ko] undefined!
> ERROR: "clear_page" [fs/fuse/fuse.ko] undefined!
> ERROR: "clear_page" [fs/ext3/ext3.ko] undefined!
> ERROR: "clear_page" [fs/ext2/ext2.ko] undefined!
> ERROR: "clear_page" [fs/exofs/libore.ko] undefined!
> ERROR: "clear_page" [fs/exofs/exofs.ko] undefined!
> ERROR: "clear_page" [drivers/block/brd.ko] undefined!
>
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
> arch/arm64/kernel/arm64ksyms.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm64/kernel/arm64ksyms.c b/arch/arm64/kernel/arm64ksyms.c
> index 7df1aad..41b4f62 100644
> --- a/arch/arm64/kernel/arm64ksyms.c
> +++ b/arch/arm64/kernel/arm64ksyms.c
> @@ -34,6 +34,7 @@ EXPORT_SYMBOL(__strnlen_user);
> EXPORT_SYMBOL(__strncpy_from_user);
>
> EXPORT_SYMBOL(copy_page);
> +EXPORT_SYMBOL(clear_page);
>
> EXPORT_SYMBOL(__copy_from_user);
> EXPORT_SYMBOL(__copy_to_user);
>
--
Chen Gang
Asianux Corporation
WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang <gang.chen@asianux.com>
To: Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Tony Lindgren <tony@atomide.com>,
"olof@lixom.net" <olof@lixom.net>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
"nico@linaro.org" <nico@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: kernel: compiling issue, need 'EXPORT_SYMBOL(clear_page)'
Date: Mon, 20 May 2013 15:15:08 +0800 [thread overview]
Message-ID: <5199CD7C.4080304@asianux.com> (raw)
In-Reply-To: <5199CCF9.4030305@asianux.com>
After this patch, can pass building arm64 with allmodconfig under
next-20130517 tree. :-)
On 05/20/2013 03:12 PM, Chen Gang wrote:
>
> Need 'EXPORT_SYMBOL(clear_page)' if building with allmodconfig.
>
> The related errors:
> ERROR: "clear_page" [fs/ocfs2/dlm/ocfs2_dlm.ko] undefined!
> ERROR: "clear_page" [fs/ntfs/ntfs.ko] undefined!
> ERROR: "clear_page" [fs/gfs2/gfs2.ko] undefined!
> ERROR: "clear_page" [fs/fuse/fuse.ko] undefined!
> ERROR: "clear_page" [fs/ext3/ext3.ko] undefined!
> ERROR: "clear_page" [fs/ext2/ext2.ko] undefined!
> ERROR: "clear_page" [fs/exofs/libore.ko] undefined!
> ERROR: "clear_page" [fs/exofs/exofs.ko] undefined!
> ERROR: "clear_page" [drivers/block/brd.ko] undefined!
>
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
> arch/arm64/kernel/arm64ksyms.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm64/kernel/arm64ksyms.c b/arch/arm64/kernel/arm64ksyms.c
> index 7df1aad..41b4f62 100644
> --- a/arch/arm64/kernel/arm64ksyms.c
> +++ b/arch/arm64/kernel/arm64ksyms.c
> @@ -34,6 +34,7 @@ EXPORT_SYMBOL(__strnlen_user);
> EXPORT_SYMBOL(__strncpy_from_user);
>
> EXPORT_SYMBOL(copy_page);
> +EXPORT_SYMBOL(clear_page);
>
> EXPORT_SYMBOL(__copy_from_user);
> EXPORT_SYMBOL(__copy_to_user);
>
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-05-20 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 7:12 [PATCH] arm64: kernel: compiling issue, need 'EXPORT_SYMBOL(clear_page)' Chen Gang
2013-05-20 7:12 ` Chen Gang
2013-05-20 7:15 ` Chen Gang [this message]
2013-05-20 7:15 ` Chen Gang
2013-05-27 10:04 ` Chen Gang
2013-05-27 10:04 ` Chen Gang
2013-05-27 10:09 ` Chen Gang
2013-05-27 10:09 ` Chen Gang
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=5199CD7C.4080304@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.