From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, jrdr.linux@gmail.com,
p76091292@gs.ncku.edu.tw, akpm@linux-foundation.org
Subject: [merged mm-stable] mm-docs-fix-comments-that-mention-mem_hotplug_end.patch removed from -mm tree
Date: Sun, 03 Jul 2022 18:10:50 -0700 [thread overview]
Message-ID: <20220704011051.0A90AC341C7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm, docs: fix comments that mention mem_hotplug_end()
has been removed from the -mm tree. Its filename was
mm-docs-fix-comments-that-mention-mem_hotplug_end.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: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
Subject: mm, docs: fix comments that mention mem_hotplug_end()
Date: Mon, 20 Jun 2022 07:15:16 +0000
Comments that mention mem_hotplug_end() are confusing as there is no
function called mem_hotplug_end(). Fix them by replacing all the
occurences of mem_hotplug_end() in the comments with mem_hotplug_done().
[akpm@linux-foundation.org: grammatical fixes]
Link: https://lkml.kernel.org/r/20220620071516.1286101-1-p76091292@gs.ncku.edu.tw
Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
Cc: Souptick Joarder <jrdr.linux@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/mmzone.h | 6 +++---
mm/compaction.c | 2 +-
mm/vmscan.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
--- a/include/linux/mmzone.h~mm-docs-fix-comments-that-mention-mem_hotplug_end
+++ a/include/linux/mmzone.h
@@ -591,8 +591,8 @@ struct zone {
* give them a chance of being in the same cacheline.
*
* Write access to present_pages at runtime should be protected by
- * mem_hotplug_begin/end(). Any reader who can't tolerant drift of
- * present_pages should get_online_mems() to get a stable value.
+ * mem_hotplug_begin/done(). Any reader who can't tolerant drift of
+ * present_pages should use get_online_mems() to get a stable value.
*/
atomic_long_t managed_pages;
unsigned long spanned_pages;
@@ -870,7 +870,7 @@ typedef struct pglist_data {
unsigned long nr_reclaim_start; /* nr pages written while throttled
* when throttling started. */
struct task_struct *kswapd; /* Protected by
- mem_hotplug_begin/end() */
+ mem_hotplug_begin/done() */
int kswapd_order;
enum zone_type kswapd_highest_zoneidx;
--- a/mm/compaction.c~mm-docs-fix-comments-that-mention-mem_hotplug_end
+++ a/mm/compaction.c
@@ -3011,7 +3011,7 @@ void kcompactd_run(int nid)
/*
* Called by memory hotplug when all memory in a node is offlined. Caller must
- * hold mem_hotplug_begin/end().
+ * be holding mem_hotplug_begin/done().
*/
void kcompactd_stop(int nid)
{
--- a/mm/vmscan.c~mm-docs-fix-comments-that-mention-mem_hotplug_end
+++ a/mm/vmscan.c
@@ -4645,7 +4645,7 @@ void kswapd_run(int nid)
/*
* Called by memory hotplug when all memory in a node is offlined. Caller must
- * hold mem_hotplug_begin/end().
+ * be holding mem_hotplug_begin/done().
*/
void kswapd_stop(int nid)
{
_
Patches currently in -mm which might be from p76091292@gs.ncku.edu.tw are
reply other threads:[~2022-07-04 1:12 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=20220704011051.0A90AC341C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=p76091292@gs.ncku.edu.tw \
/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.