From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
damon@lists.linux.dev, SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 7.2.y] mm/damon/core: skip aging from repeated aggressive merging
Date: Fri, 11 Sep 2026 07:20:57 -0400 [thread overview]
Message-ID: <daily-reply-0038-re-damon-skip-aging-7-2@kernel.org> (raw)
In-Reply-To: <20260910005213.126528-1-sj@kernel.org>
> The number of DAMON regions could temporarily exceed the user-defined
> maximum number of regions limit for corner cases. For example, users
> could lower the limit via runtime parameters update.
Queued for 7.2, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-11 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 12:52 FAILED: patch "[PATCH] mm/damon/core: skip aging from repeated aggressive merging" failed to apply to 7.2-stable tree gregkh
2026-09-09 4:34 ` [PATCH 7.2.y] mm/damon/core: skip aging from repeated aggressive merging SJ Park
2026-09-09 12:19 ` Greg KH
2026-09-10 1:02 ` SJ Park
2026-09-10 6:15 ` Greg KH
2026-09-10 13:50 ` SJ Park
2026-09-10 0:52 ` SJ Park
2026-09-11 11:20 ` Sasha Levin [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=daily-reply-0038-re-damon-skip-aging-7-2@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=sj@kernel.org \
--cc=stable@vger.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