From: Yajun Deng <yajun.deng@linux.dev>
To: rppt@kernel.org, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Yajun Deng <yajun.deng@linux.dev>
Subject: [PATCH] mm/mm_init.c: remove redundant pr_info when node is memoryless
Date: Wed, 6 Sep 2023 17:11:13 +0800 [thread overview]
Message-ID: <20230906091113.4029983-1-yajun.deng@linux.dev> (raw)
There is a similar pr_info in free_area_init_node(), so remove the
redundant pr_info.
Signed-off-by: Yajun Deng <yajun.deng@linux.dev>
---
mm/mm_init.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mm/mm_init.c b/mm/mm_init.c
index 50f2f34745af..6be6f50813b1 100644
--- a/mm/mm_init.c
+++ b/mm/mm_init.c
@@ -1871,8 +1871,6 @@ void __init free_area_init(unsigned long *max_zone_pfn)
pg_data_t *pgdat;
if (!node_online(nid)) {
- pr_info("Initializing node %d as memoryless\n", nid);
-
/* Allocator not initialized yet */
pgdat = arch_alloc_nodedata(nid);
if (!pgdat)
--
2.25.1
next reply other threads:[~2023-09-06 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:11 Yajun Deng [this message]
2023-09-10 21:30 ` Andrew Morton
2023-09-11 2:57 ` Yajun Deng
2023-09-11 7:51 ` David Hildenbrand
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=20230906091113.4029983-1-yajun.deng@linux.dev \
--to=yajun.deng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@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