From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Xuefeng Li <lixuefeng@loongson.cn>,
linux-mips@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v5 4/4] MIPS: Remove not used variable usermem
Date: Sat, 5 Mar 2022 14:21:29 +0800 [thread overview]
Message-ID: <1646461289-31992-5-git-send-email-yangtiezhu@loongson.cn> (raw)
In-Reply-To: <1646461289-31992-1-git-send-email-yangtiezhu@loongson.cn>
Now, the variable usermem is not used any more, just remove it.
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
---
arch/mips/kernel/setup.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
index 6b7229f..e9408a5 100644
--- a/arch/mips/kernel/setup.c
+++ b/arch/mips/kernel/setup.c
@@ -338,7 +338,6 @@ static void __init bootmem_init(void)
#endif /* CONFIG_SGI_IP27 */
-static int usermem __initdata;
static phys_addr_t memory_limit;
static phys_addr_t memory_base;
@@ -632,10 +631,6 @@ static void __init arch_mem_init(char **cmdline_p)
*cmdline_p = command_line;
parse_early_param();
-
- if (usermem)
- pr_info("User-defined physical RAM map overwrite\n");
-
check_kernel_sections_mem();
early_init_fdt_reserve_self();
--
2.1.0
prev parent reply other threads:[~2022-03-05 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 6:21 [PATCH v5 0/4] MIPS: Modify mem= and memmap= parameter Tiezhu Yang
2022-03-05 6:21 ` [PATCH v5 1/4] memblock: Introduce memblock_mem_range_remove_map() Tiezhu Yang
2022-03-05 13:28 ` Mike Rapoport
2022-03-05 6:21 ` [PATCH v5 2/4] MIPS: Refactor early_parse_mem() to fix mem= parameter Tiezhu Yang
2022-03-05 6:21 ` [PATCH v5 3/4] MIPS: Refactor early_parse_memmap() to fix memmap= parameter Tiezhu Yang
2022-03-05 6:21 ` Tiezhu Yang [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=1646461289-31992-5-git-send-email-yangtiezhu@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lixuefeng@loongson.cn \
--cc=rppt@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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.