From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
Nick Hu <nickhu@andestech.com>, Greentime Hu <green.hu@gmail.com>
Subject: [PATCH 08/15] nds32: convert to setup_initial_init_mm()
Date: Sat, 29 May 2021 18:54:57 +0800 [thread overview]
Message-ID: <20210529105504.180544-9-wangkefeng.wang@huawei.com> (raw)
In-Reply-To: <20210529105504.180544-1-wangkefeng.wang@huawei.com>
Use setup_initial_init_mm() helper to simplify code.
Cc: Nick Hu <nickhu@andestech.com>
Cc: Greentime Hu <green.hu@gmail.com>
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
---
arch/nds32/kernel/setup.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/arch/nds32/kernel/setup.c b/arch/nds32/kernel/setup.c
index af82e996f412..41725eaf8bac 100644
--- a/arch/nds32/kernel/setup.c
+++ b/arch/nds32/kernel/setup.c
@@ -294,10 +294,7 @@ void __init setup_arch(char **cmdline_p)
setup_cpuinfo();
- init_mm.start_code = (unsigned long)&_stext;
- init_mm.end_code = (unsigned long)&_etext;
- init_mm.end_data = (unsigned long)&_edata;
- init_mm.brk = (unsigned long)&_end;
+ setup_initial_init_mm(_stext, _etext, _edata, _end);
/* setup bootmem allocator */
setup_memory();
--
2.26.2
next prev parent reply other threads:[~2021-05-29 10:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 10:54 [PATCH 00/15] init_mm: setup init_mm text/data/brk by new setup_initial_init_mm() helper Kefeng Wang
2021-05-29 10:54 ` [PATCH 01/15] mm: add " Kefeng Wang
2021-05-31 7:45 ` Geert Uytterhoeven
2021-05-31 13:42 ` Kefeng Wang
2021-05-29 10:54 ` [PATCH 02/15] arc: convert to setup_initial_init_mm() Kefeng Wang
2021-05-29 10:54 ` Kefeng Wang
2021-05-29 10:54 ` [PATCH 03/15] arm: " Kefeng Wang
2021-05-29 10:54 ` Kefeng Wang
2021-05-29 12:18 ` Russell King (Oracle)
2021-05-29 12:18 ` Russell King (Oracle)
2021-05-31 1:10 ` Kefeng Wang
2021-05-31 1:10 ` Kefeng Wang
2021-05-29 10:54 ` [PATCH 04/15] arm64: " Kefeng Wang
2021-05-29 10:54 ` Kefeng Wang
2021-05-29 10:54 ` [PATCH 05/15] csky: " Kefeng Wang
2021-05-30 0:23 ` Guo Ren
2021-05-29 10:54 ` [PATCH 06/15] h8300: " Kefeng Wang
2021-05-31 7:48 ` Geert Uytterhoeven
2021-05-29 10:54 ` [PATCH 07/15] m68k: " Kefeng Wang
2021-05-31 7:48 ` Geert Uytterhoeven
2021-06-02 13:13 ` Greg Ungerer
2021-05-29 10:54 ` Kefeng Wang [this message]
2021-05-29 10:54 ` [PATCH 09/15] nios2: " Kefeng Wang
2021-05-29 10:54 ` [PATCH 10/15] openrisc: " Kefeng Wang
2021-05-29 10:54 ` [OpenRISC] " Kefeng Wang
2021-05-29 13:48 ` Stafford Horne
2021-05-29 13:48 ` [OpenRISC] " Stafford Horne
2021-05-29 10:55 ` [PATCH 11/15] powerpc: " Kefeng Wang
2021-05-29 10:55 ` Kefeng Wang
2021-05-29 12:46 ` Santosh Sivaraj
2021-05-29 15:22 ` Christophe Leroy
2021-05-29 15:22 ` Christophe Leroy
2021-05-31 1:02 ` Kefeng Wang
2021-05-31 1:02 ` Kefeng Wang
2021-05-29 16:16 ` Christophe Leroy
2021-05-29 16:16 ` Christophe Leroy
2021-05-31 1:05 ` Kefeng Wang
2021-05-31 1:05 ` Kefeng Wang
2021-05-29 10:55 ` [PATCH 12/15] riscv: " Kefeng Wang
2021-05-29 10:55 ` Kefeng Wang
2021-05-29 10:55 ` [PATCH 13/15] s390: " Kefeng Wang
2021-05-29 10:55 ` [PATCH 14/15] sh: " Kefeng Wang
2021-05-29 10:55 ` [PATCH 15/15] x86: " Kefeng Wang
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=20210529105504.180544-9-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=green.hu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickhu@andestech.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 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.