From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rppt@kernel.org,fancer.lancer@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-mm_initc-append-newline-to-the-unavailable-ranges-log-message.patch removed from -mm tree
Date: Sun, 10 Dec 2023 16:55:20 -0800 [thread overview]
Message-ID: <20231211005520.EB3A8C433C8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/mm_init.c: append newline to the unavailable ranges log-message
has been removed from the -mm tree. Its filename was
mm-mm_initc-append-newline-to-the-unavailable-ranges-log-message.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Serge Semin <fancer.lancer@gmail.com>
Subject: mm/mm_init.c: append newline to the unavailable ranges log-message
Date: Wed, 22 Nov 2023 21:24:04 +0300
Based on the init_unavailable_range() method and it's callee semantics no
multi-line info messages are intended to be printed to the console. Thus
append the '\n' symbol to the respective info string.
Link: https://lkml.kernel.org/r/20231122182419.30633-7-fancer.lancer@gmail.com
Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/mm_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/mm_init.c~mm-mm_initc-append-newline-to-the-unavailable-ranges-log-message
+++ a/mm/mm_init.c
@@ -827,7 +827,7 @@ static void __init init_unavailable_rang
}
if (pgcnt)
- pr_info("On node %d, zone %s: %lld pages in unavailable ranges",
+ pr_info("On node %d, zone %s: %lld pages in unavailable ranges\n",
node, zone_names[zone], pgcnt);
}
_
Patches currently in -mm which might be from fancer.lancer@gmail.com are
reply other threads:[~2023-12-11 0:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231211005520.EB3A8C433C8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=fancer.lancer@gmail.com \
--cc=mm-commits@vger.kernel.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 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.