From: SeongJae Park <sj@kernel.org>
To: Liew Rui Yan <aethernet65535@gmail.com>
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: (sashiko review) [PATCH v4 1/2] mm/damon/lru_sort: validate min_region_size to be power of 2
Date: Sun, 12 Apr 2026 14:37:19 -0700 [thread overview]
Message-ID: <20260412213720.89145-1-sj@kernel.org> (raw)
In-Reply-To: <20260412190455.6685-1-aethernet65535@gmail.com>
Hi Liew,
On Mon, 13 Apr 2026 03:04:55 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> Hi SeongJae,
>
> Thank you for your detailed explanation and for being patient with me. I
> sincerely apologize for the confusion and the extra workload my unclear
> communication has caused you. It was never my intention to hide context
> or game the system; I simply misjudged the priorities and failed to
> provide the full picture.
>
> I want to continue contributing to DAMON. I truly enjoy working on it,
> and I'm grateful for the opportunity.
Thank you for your detailed explanations of the context. Those all make sense
to me. Also appreciate your will to continue the contributions. :)
[...]
> > Next Steps
> > ----------
> >
> > So, what to do? Please prioritize series B, if you still willing to do. It is
> > ok to keep doing series A, but only as the minor user experience improvement.
> > Clearly explain the whole context you are aware of. Don't Cc stable@ for
> > series A, as it is only an incomplete fix of it. The fix of the one trigger
> > point is just a side effect.
>
> Yes, I absolutely want to continue contributing to DAMON.
>
> I realize most of this confusion came from me misinterpreting your words
> or making assumptions without asking. So this time, I want to be
> explicit:
> 1. I will remove the Cc stable@
Please also make the description of the patch clear.
> 2. Since you suggested prioritizing Series B, would you prefer me to
> send a revised v5 of Series A now, or should I wait until Series B is
> settled to avoid more noise in your inbox?
Please work in your pace :) Pick whatever you willing to work first.
I'd like to avoid delaying series B too long, though. The bug is not very
critical, but better to be fixed sooner than later. If you have no enough
capacity, please feel free to hand it over to me.
> 3. I will focus on Series B starting now.
Sounds good.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-04-12 21:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 4:42 [PATCH v4 0/2] mm/damon: " Liew Rui Yan
2026-04-10 4:42 ` [PATCH v4 1/2] mm/damon/lru_sort: " Liew Rui Yan
2026-04-10 9:40 ` (sashiko review) " Liew Rui Yan
2026-04-10 13:55 ` SeongJae Park
2026-04-10 16:46 ` Liew Rui Yan
2026-04-10 17:00 ` SeongJae Park
2026-04-10 23:24 ` SeongJae Park
2026-04-11 0:04 ` Liew Rui Yan
2026-04-11 15:38 ` SeongJae Park
2026-04-12 19:04 ` Liew Rui Yan
2026-04-12 21:37 ` SeongJae Park [this message]
2026-04-10 13:56 ` SeongJae Park
2026-04-10 4:42 ` [PATCH v4 2/2] mm/damon/reclaim: " Liew Rui Yan
2026-04-10 10:08 ` (sashiko review) " Liew Rui Yan
2026-04-10 13:44 ` SeongJae Park
2026-04-10 13:57 ` SeongJae Park
2026-04-10 14:05 ` [PATCH v4 0/2] mm/damon: " SeongJae 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=20260412213720.89145-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.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