From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>
Cc: <linux-mm@kvack.org>, Kefeng Wang <wangkefeng.wang@huawei.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
<linux-s390@vger.kernel.org>
Subject: [PATCH v2 13/15] s390: convert to setup_initial_init_mm()
Date: Fri, 4 Jun 2021 15:06:31 +0800 [thread overview]
Message-ID: <20210604070633.32363-14-wangkefeng.wang@huawei.com> (raw)
In-Reply-To: <20210604070633.32363-1-wangkefeng.wang@huawei.com>
Use setup_initial_init_mm() helper to simplify code.
Cc: Heiko Carstens <hca@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-s390@vger.kernel.org
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
---
arch/s390/kernel/setup.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/arch/s390/kernel/setup.c b/arch/s390/kernel/setup.c
index 5aab59ad5688..e1793ed43510 100644
--- a/arch/s390/kernel/setup.c
+++ b/arch/s390/kernel/setup.c
@@ -1119,10 +1119,7 @@ void __init setup_arch(char **cmdline_p)
ROOT_DEV = Root_RAM0;
- init_mm.start_code = (unsigned long) _text;
- init_mm.end_code = (unsigned long) _etext;
- init_mm.end_data = (unsigned long) _edata;
- init_mm.brk = (unsigned long) _end;
+ setup_initial_init_mm(_text, _etext, _edata, _end);
if (IS_ENABLED(CONFIG_EXPOLINE_AUTO))
nospec_auto_detect();
--
2.26.2
next prev parent reply other threads:[~2021-06-04 6:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 7:06 [PATCH v2 00/15] init_mm: cleanup ARCH's text/data/brk setup code Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 01/15] mm: add setup_initial_init_mm() helper Kefeng Wang
2021-06-06 21:31 ` Mike Rapoport
2021-06-07 1:50 ` Kefeng Wang
2021-06-07 2:36 ` [PATCH v3] " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 02/15] arc: convert to setup_initial_init_mm() Kefeng Wang
2021-06-04 14:03 ` Vineet Gupta
2021-06-04 7:06 ` [PATCH v2 03/15] arm: " Kefeng Wang
2021-06-07 9:25 ` Russell King (Oracle)
2021-06-04 7:06 ` [PATCH v2 04/15] arm64: " Kefeng Wang
2021-06-04 9:19 ` Catalin Marinas
2021-06-04 7:06 ` [PATCH v2 05/15] csky: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 06/15] h8300: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 07/15] m68k: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 08/15] nds32: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 09/15] nios2: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 10/15] openrisc: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 11/15] powerpc: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 12/15] riscv: " Kefeng Wang
2021-06-12 3:55 ` Palmer Dabbelt
2021-06-04 7:06 ` Kefeng Wang [this message]
2021-06-04 7:06 ` [PATCH v2 14/15] sh: " Kefeng Wang
2021-06-04 7:06 ` [PATCH v2 15/15] x86: " Kefeng Wang
2021-06-08 0:26 ` Andrew Morton
2021-06-08 1:39 ` Kefeng Wang
2021-06-06 21:29 ` [PATCH v2 00/15] init_mm: cleanup ARCH's text/data/brk setup code Mike Rapoport
2021-06-07 0:55 ` Kefeng Wang
2021-06-07 5:48 ` Christophe Leroy
2021-06-07 8:30 ` Kefeng Wang
2021-06-07 9:31 ` Russell King (Oracle)
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=20210604070633.32363-14-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@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 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).