From: guoren@kernel.org
To: linux-csky@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
arnd@arndb.de, Guo Ren <ren_guo@c-sky.com>,
Mo Qihui <qihui.mo@verisilicon.com>,
Zhange Jian <zhang_jian5@dahuatech.com>
Subject: [PATCH 5/5] csky/mm: Fixup export invalid_pte_table symbol
Date: Mon, 30 Dec 2019 16:23:31 +0800 [thread overview]
Message-ID: <20191230082331.30976-5-guoren@kernel.org> (raw)
In-Reply-To: <20191230082331.30976-1-guoren@kernel.org>
From: Guo Ren <ren_guo@c-sky.com>
There is no present bit in csky pmd hardware, so we need to prepare invalid_pte_table
for empty pmd entry and the functions (pmd_none & pmd_present) in pgtable.h need
invalid_pte_talbe to get result. If a module use these functions, we need export the
symbol for it.
Signed-off-by: Guo Ren <ren_guo@c-sky.com>
Cc: Mo Qihui <qihui.mo@verisilicon.com>
Cc: Zhange Jian <zhang_jian5@dahuatech.com>
---
arch/csky/mm/init.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/csky/mm/init.c b/arch/csky/mm/init.c
index 322eb7bd7962..dbb4b2dfe4b7 100644
--- a/arch/csky/mm/init.c
+++ b/arch/csky/mm/init.c
@@ -31,6 +31,7 @@
pgd_t swapper_pg_dir[PTRS_PER_PGD] __page_aligned_bss;
pte_t invalid_pte_table[PTRS_PER_PTE] __page_aligned_bss;
+EXPORT_SYMBOL(invalid_pte_table);
unsigned long empty_zero_page[PAGE_SIZE / sizeof(unsigned long)]
__page_aligned_bss;
EXPORT_SYMBOL(empty_zero_page);
--
2.17.0
prev parent reply other threads:[~2019-12-30 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 8:23 [PATCH 1/5] MAINTAINERS: csky: Add mailing list for csky guoren
2019-12-30 8:23 ` [PATCH 2/5] csky: Initial stack protector support guoren
2019-12-30 8:23 ` [PATCH 3/5] csky: Tightly-Coupled Memory or Sram support guoren
2019-12-30 8:23 ` [PATCH 4/5] csky: Separate fixaddr_init from highmem guoren
2019-12-30 8:23 ` guoren [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=20191230082331.30976-5-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qihui.mo@verisilicon.com \
--cc=ren_guo@c-sky.com \
--cc=zhang_jian5@dahuatech.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).