From: "T.J. Mercier" <tjmercier@google.com>
To: Kinsey Ho <kinseyho@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, Yosry Ahmed <yosryahmed@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>, Tejun Heo <tj@kernel.org>,
Zefan Li <lizefan.x@bytedance.com>,
mkoutny@suse.com
Subject: Re: [PATCH mm-unstable v3 5/5] mm: clean up mem_cgroup_iter()
Date: Wed, 28 Aug 2024 10:49:26 -0700 [thread overview]
Message-ID: <CABdmKX2GbvqtB2dED7hNKYtMLwu=akanYUVN3DS3Vtgbcde8bw@mail.gmail.com> (raw)
In-Reply-To: <20240827230753.2073580-6-kinseyho@google.com>
On Tue, Aug 27, 2024 at 4:11 PM Kinsey Ho <kinseyho@google.com> wrote:
>
> A clean up to make variable names more clear and to improve code
> readability.
>
> No functional change.
>
> Signed-off-by: Kinsey Ho <kinseyho@google.com>
Reviewed-by: T.J. Mercier <tjmercier@google.com>
prev parent reply other threads:[~2024-08-28 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 23:07 [PATCH mm-unstable v3 0/5] Improve mem_cgroup_iter() Kinsey Ho
2024-08-27 23:07 ` [PATCH mm-unstable v3 1/5] cgroup: clarify css sibling linkage is protected by cgroup_mutex or RCU Kinsey Ho
2024-08-27 23:07 ` [PATCH mm-unstable v3 2/5] mm: don't hold css->refcnt during traversal Kinsey Ho
2024-08-28 17:58 ` T.J. Mercier
2024-08-27 23:07 ` [PATCH mm-unstable v3 3/5] mm: increment gen # before restarting traversal Kinsey Ho
2024-08-28 17:49 ` T.J. Mercier
2024-08-27 23:07 ` [PATCH mm-unstable v3 4/5] mm: restart if multiple traversals raced Kinsey Ho
2024-08-28 17:49 ` T.J. Mercier
2024-08-30 10:04 ` Hugh Dickins
2024-08-30 17:45 ` Kinsey Ho
2024-08-30 19:04 ` Yu Zhao
2024-08-27 23:07 ` [PATCH mm-unstable v3 5/5] mm: clean up mem_cgroup_iter() Kinsey Ho
2024-08-28 17:49 ` T.J. Mercier [this message]
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='CABdmKX2GbvqtB2dED7hNKYtMLwu=akanYUVN3DS3Vtgbcde8bw@mail.gmail.com' \
--to=tjmercier@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kinseyho@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tj@kernel.org \
--cc=yosryahmed@google.com \
/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