From: Mukesh Ojha <quic_mojha@quicinc.com>
To: <cgel.zte@gmail.com>, <hannes@cmpxchg.org>
Cc: <mhocko@kernel.org>, <roman.gushchin@linux.dev>,
<shakeelb@google.com>, <songmuchun@bytedance.com>,
<akpm@linux-foundation.org>, <cgroups@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
xupanda <xu.panda@zte.com.cn>, Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH v2 linux-next] mm: memcontrol: Fix a typo in comment
Date: Mon, 15 Aug 2022 20:26:01 +0530 [thread overview]
Message-ID: <4323bf73-7a29-7a0e-55ef-b75fcfa76414@quicinc.com> (raw)
In-Reply-To: <20220815065102.74347-1-xu.panda@zte.com.cn>
On 8/15/2022 12:21 PM, cgel.zte@gmail.com wrote:
> From: xupanda <xu.panda@zte.com.cn>
>
> Fix a spelling mistake in comment.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: xupanda <xu.panda@zte.com.cn>
> Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
>
> ---
> Change for v2:
> - fix wrong title
> ---
>
> mm/memcontrol.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletion(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index b69979c9ced5..4dddd8be320a 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1143,7 +1143,7 @@ static void invalidate_reclaim_iterators(struct mem_cgroup *dead_memcg)
> } while ((memcg = parent_mem_cgroup(memcg)));
>
> /*
> - * When cgruop1 non-hierarchy mode is used,
> + * When cgroup1 non-hierarchy mode is used,
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
-Mukesh
> * parent_mem_cgroup() does not walk all the way up to the
> * cgroup root (root_mem_cgroup). So we have to handle
> * dead_memcg from cgroup root separately.
prev parent reply other threads:[~2022-08-15 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 6:51 cgel.zte
2022-08-15 14:56 ` Mukesh Ojha [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=4323bf73-7a29-7a0e-55ef-b75fcfa76414@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=cgel.zte@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=xu.panda@zte.com.cn \
--cc=zealci@zte.com.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