From: Donet Tom <donettom@linux.ibm.com>
To: Xiang Gao <gxxa03070307@gmail.com>,
akpm@linux-foundation.org, axelrasmussen@google.com,
yuanchu@google.com, hannes@cmpxchg.org
Cc: weixugc@google.com, david@kernel.org, mhocko@kernel.org,
zhengqi.arch@bytedance.com, shakeel.butt@linux.dev,
ljs@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Xiang Gao <gaoxiang17@xiaomi.com>
Subject: Re: [PATCH] mm/vmscan: fix typos in comments
Date: Thu, 16 Apr 2026 10:10:12 +0530 [thread overview]
Message-ID: <87167cf2-5851-46a5-99bf-deb5894ff214@linux.ibm.com> (raw)
In-Reply-To: <20260416024248.687943-1-gxxa03070307@gmail.com>
Hi
On 4/16/26 8:12 AM, Xiang Gao wrote:
> From: Xiang Gao <gaoxiang17@xiaomi.com>
>
> Fix three typos in comments:
>
> - Line 112: "zome_reclaim_mode" -> "zone_reclaim_mode"
> - Line 6208: "prioities" -> "priorities"
> - Line 7067: "that that high" -> "that the high" (duplicated word)
>
> Signed-off-by: gaoxiang17 <gaoxiang17@xiaomi.com>
I am seeing below issue with checkpatch.pl
./scripts/checkpatch.pl --strict 0001-mm-vmscan-fix-typos-in-comments.patch
WARNING: From:/Signed-off-by: email name mismatch: 'From: Xiang Gao
<gaoxiang17@xiaomi.com>' != 'Signed-off-by: gaoxiang17
<gaoxiang17@xiaomi.com>'
total: 0 errors, 1 warnings, 0 checks, 24 lines checked
> ---
> mm/vmscan.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 0fc9373e8251..710fbe1ee151 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -109,7 +109,7 @@ struct scan_control {
> /* zone_reclaim_mode */
> unsigned int may_unmap:1;
>
> - /* zome_reclaim_mode, boost reclaim, cgroup restrictions */
> + /* zone_reclaim_mode, boost reclaim, cgroup restrictions */
> unsigned int may_swap:1;
>
> /* Not allow cache_trim_mode to be turned on as part of reclaim? */
> @@ -6205,7 +6205,7 @@ static void consider_reclaim_throttle(pg_data_t *pgdat, struct scan_control *sc)
> if (current_is_kswapd() || cgroup_reclaim(sc))
> return;
>
> - /* Throttle if making no progress at high prioities. */
> + /* Throttle if making no progress at high priorities. */
> if (sc->priority == 1 && !sc->nr_reclaimed)
> reclaim_throttle(pgdat, VMSCAN_THROTTLE_NOPROGRESS);
> }
> @@ -7064,7 +7064,7 @@ static int balance_pgdat(pg_data_t *pgdat, int order, int highest_zoneidx)
>
> /*
> * There should be no need to raise the scanning priority if
> - * enough pages are already being scanned that that high
> + * enough pages are already being scanned that the high
> * watermark would be met at 100% efficiency.
> */
> if (kswapd_shrink_node(pgdat, &sc))
next prev parent reply other threads:[~2026-04-16 4:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 2:42 Xiang Gao
2026-04-16 4:02 ` Donet Tom
2026-04-16 4:40 ` Donet Tom [this message]
2026-04-16 5:18 ` 答复: [External Mail]Re: " 高翔
2026-04-16 4:49 ` Barry Song
2026-04-16 5:18 ` 答复: [External Mail]Re: " 高翔
2026-04-16 5:15 ` [PATCH v2] " Xiang Gao
2026-04-16 5:47 ` Donet Tom
2026-04-16 6:23 ` 答复: [External Mail]Re: " 高翔
2026-04-16 6:25 ` 高翔
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=87167cf2-5851-46a5-99bf-deb5894ff214@linux.ibm.com \
--to=donettom@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@kernel.org \
--cc=gaoxiang17@xiaomi.com \
--cc=gxxa03070307@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.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