From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,harry@kernel.org,zhangguopeng@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-memcg-remove-stray-text-from-obj_stock_pcp-comment.patch removed from -mm tree
Date: Tue, 28 Jul 2026 21:13:01 -0700 [thread overview]
Message-ID: <20260729041302.3FD711F000E9@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: memcg: remove stray text from obj_stock_pcp comment
has been removed from the -mm tree. Its filename was
mm-memcg-remove-stray-text-from-obj_stock_pcp-comment.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: Guopeng Zhang <zhangguopeng@kylinos.cn>
Subject: mm: memcg: remove stray text from obj_stock_pcp comment
Date: Tue, 23 Jun 2026 16:26:14 +0800
A patch filename was accidentally inserted into the comment describing
the nr_bytes field of struct obj_stock_pcp. Remove it.
No functional change.
Link: https://lore.kernel.org/20260623082614.81621-1-guopeng.zhang@linux.dev
Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
Acked-by: Harry Yoo (Oracle) <harry@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/memcontrol.c~mm-memcg-remove-stray-text-from-obj_stock_pcp-comment
+++ a/mm/memcontrol.c
@@ -2039,7 +2039,7 @@ struct obj_stock_pcp {
/*
* On rare archs with 256KiB base page size (hexagon and powerpc 44x)
* keep nr_bytes to unsigned int as uint16_t cannot represent the full
-e patches/memcg-uint16_t-for-nr_bytes-in-obj_stock_pcp.patch * sub-page remainder. Such archs are not cacheline optimization target.
+ * sub-page remainder. Such archs are not cacheline optimization targets.
*/
unsigned int nr_bytes[NR_OBJ_STOCK];
#else
_
Patches currently in -mm which might be from zhangguopeng@kylinos.cn are
mm-memcontrol-update-state_local-when-flushing-nmi-stats.patch
mm-memcg-v1-account-vmpressure-event-allocations.patch
mm-memcg-v1-fix-wrong-linux-mm-list-address-in-deprecation-warnings.patch
mm-memcontrol-drop-unused-cpu-argument-from-flush_nmi_stats.patch
mm-memcontrol-factor-out-memcg-kmem-uncharge-sequence.patch
mm-memcg-v1-make-mem_cgroup_oom_notify_cb-return-void.patch
mm-memcg-stop-reclaim-when-a-limit-update-is-superseded.patch
reply other threads:[~2026-07-29 4:13 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=20260729041302.3FD711F000E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=harry@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=zhangguopeng@kylinos.cn \
/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