From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guan Xuetao <gxt@mprc.pku.edu.cn>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/3] arch: unicore32: ksyms: export '__cpuc_coherent_kern_range' to avoid compiling failure
Date: Tue, 27 May 2014 08:08:06 +0800 [thread overview]
Message-ID: <5383D766.7070106@gmail.com> (raw)
In-Reply-To: <5383D5F5.2000303@gmail.com>
flush_icache_range() is '__cpuc_coherent_kern_range' under unicore32,
and lkdtm.ko needs it. At present, '__cpuc_coherent_kern_range' is
still used by unicore32, so export it to avoid compiling failure.
The related error (with allmodconfig under unicore32):
ERROR: "__cpuc_coherent_kern_range" [drivers/misc/lkdtm.ko] undefined!
Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
arch/unicore32/mm/proc-syms.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/unicore32/mm/proc-syms.c b/arch/unicore32/mm/proc-syms.c
index f30071e..21c00fc 100644
--- a/arch/unicore32/mm/proc-syms.c
+++ b/arch/unicore32/mm/proc-syms.c
@@ -19,5 +19,7 @@
EXPORT_SYMBOL(cpu_dcache_clean_area);
EXPORT_SYMBOL(cpu_set_pte);
+EXPORT_SYMBOL(__cpuc_coherent_kern_range);
+
EXPORT_SYMBOL(__cpuc_dma_flush_range);
EXPORT_SYMBOL(__cpuc_dma_clean_range);
--
1.9.2.459.g68773ac
next prev parent reply other threads:[~2014-05-27 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 0:01 [PATCH 0/3] arch: unicore32: ksyms: export several implemeted symbols to avoid compiling failure Chen Gang
2014-05-27 0:03 ` [PATCH 1/3] arch: unicore32: ksyms: export additional find_first_*() " Chen Gang
2014-05-27 0:13 ` 回复: " 管雪涛
2014-05-27 0:04 ` [PATCH 2/3] arch: unicore32: ksyms: export 'pm_power_off' " Chen Gang
2014-05-27 0:14 ` 回复: " 管雪涛
2014-05-27 0:08 ` Chen Gang [this message]
2014-05-27 0:14 ` 回复: [PATCH 3/3] arch: unicore32: ksyms: export '__cpuc_coherent_kern_range' " 管雪涛
2014-05-27 0:13 ` 回复: [PATCH 0/3] arch: unicore32: ksyms: export several implemeted symbols " 管雪涛
2014-05-27 0:32 ` 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=5383D766.7070106@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-kernel@vger.kernel.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.