From: Zenghui Yu <zenghui.yu@linux.dev>
To: "Adrian Huang (Lenovo)" <adrianhuang0701@gmail.com>
Cc: SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ahuang12@lenovo.com
Subject: Re: [PATCH 1/1] mm/damon: fix typos in comments
Date: Tue, 15 Sep 2026 21:00:01 +0800 [thread overview]
Message-ID: <166d8533-127c-4e2b-b37e-a6650c981a97@linux.dev> (raw)
In-Reply-To: <20260915102746.647-1-adrianhuang0701@gmail.com>
On 9/15/26 6:27 PM, Adrian Huang (Lenovo) wrote:
> Correct spelling mistakes. No functional changes.
>
> Signed-off-by: Adrian Huang (Lenovo) <adrianhuang0701@gmail.com>
> ---
> mm/damon/core.c | 6 +++---
> mm/damon/lru_sort.c | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index 0c98f7e267d0..981a153619c0 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
> @@ -2447,7 +2447,7 @@ static bool damos_valid_target(struct damon_ctx *c, struct damon_region *r,
> * This function checks if a given region should be skipped or not for the
> * reason. If only the starting part of the region has previously charged,
> * this function splits the region into two so that the second one covers the
> - * area that not charged in the previous charge widnow, and return true. The
> + * area that not charged in the previous charge window, and return true. The
> * caller can see the second one on the next iteration of the region walk.
> * Note that this means the caller should use damon_for_each_region() instead
> * of damon_for_each_region_safe(). If damon_for_each_region_safe() is used,
> @@ -2613,7 +2613,7 @@ static void damos_walk_call_walk(struct damon_ctx *ctx, struct damon_target *t,
> * This function is called when kdamond finished applying the action of a DAMOS
> * scheme to all regions that eligible for the given &damos->apply_interval_us.
> * If every scheme of @ctx including @s now finished walking for at least one
> - * &damos->apply_interval_us, this function makrs the handling of the given
> + * &damos->apply_interval_us, this function marks the handling of the given
> * DAMOS walk request is done, so that damos_walk() can wake up and return.
> */
> static void damos_walk_complete(struct damon_ctx *ctx, struct damos *s)
> @@ -4143,7 +4143,7 @@ static bool damon_find_system_rams_range(unsigned long *start,
> * This function sets the region of @t as requested by @start and @end. If the
> * values of @start and @end are zero, however, this function finds 'System
> * RAM' resources and sets the region to cover all the resource. In the latter
> - * case, this function saves the start and the end addresseses of the first and
> + * case, this function saves the start and the end addresses of the first and
> * the last resources in @start and @end, respectively.
> *
> * Return: 0 on success, negative error code otherwise.
> diff --git a/mm/damon/lru_sort.c b/mm/damon/lru_sort.c
> index ad8e86dd3a93..273efa3c913e 100644
> --- a/mm/damon/lru_sort.c
> +++ b/mm/damon/lru_sort.c
> @@ -260,7 +260,7 @@ static int damon_lru_sort_add_filters(struct damos *hot_scheme,
> return -ENOMEM;
> damos_add_filter(hot_scheme, filter);
>
> - /* disabllow de-prioritizing young pages */
> + /* disallow de-prioritizing young pages */
> filter = damos_new_filter(DAMOS_FILTER_TYPE_YOUNG, true, false);
> if (!filter)
> return -ENOMEM;
Reviewed-by: Zenghui Yu (Huawei) <zenghui.yu@linux.dev>
Thanks,
Zenghui
next prev parent reply other threads:[~2026-09-15 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 10:27 Adrian Huang (Lenovo)
2026-09-15 13:00 ` Zenghui Yu [this message]
2026-09-15 15:07 ` SJ Park
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=166d8533-127c-4e2b-b37e-a6650c981a97@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®