From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, tj@kernel.org, shakeelb@google.com,
roman.gushchin@linux.dev, muchun.song@linux.dev,
hannes@cmpxchg.org, mhocko@suse.com, akpm@linux-foundation.org
Subject: [folded-merged] memcg-drop-kmemlimit_in_bytes-fix.patch removed from -mm tree
Date: Fri, 11 Aug 2023 15:22:56 -0700 [thread overview]
Message-ID: <20230811222257.043EDC433C7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: memcg-drop-kmemlimit_in_bytes-fix
has been removed from the -mm tree. Its filename was
memcg-drop-kmemlimit_in_bytes-fix.patch
This patch was dropped because it was folded into memcg-drop-kmemlimit_in_bytes.patch
------------------------------------------------------
From: Michal Hocko <mhocko@suse.com>
Subject: memcg-drop-kmemlimit_in_bytes-fix
Date: Fri, 7 Jul 2023 09:07:47 +0200
restore _KMEM switch case
Link: https://lkml.kernel.org/r/ZKe5wxdbvPi5Cwd7@dhcp22.suse.cz
Signed-off-by: Michal Hocko <mhocko@suse.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Muchun Song <muchun.song@linux.dev>
Cc: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Shakeel Butt <shakeelb@google.com>
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memcontrol.c | 3 +++
1 file changed, 3 insertions(+)
--- a/mm/memcontrol.c~memcg-drop-kmemlimit_in_bytes-fix
+++ a/mm/memcontrol.c
@@ -3708,6 +3708,9 @@ static u64 mem_cgroup_read_u64(struct cg
case _MEMSWAP:
counter = &memcg->memsw;
break;
+ case _KMEM:
+ counter = &memcg->kmem;
+ break;
case _TCP:
counter = &memcg->tcpmem;
break;
_
Patches currently in -mm which might be from mhocko@suse.com are
memcg-drop-kmemlimit_in_bytes.patch
reply other threads:[~2023-08-11 22:23 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=20230811222257.043EDC433C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=tj@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.