public inbox for damon@lists.linux.dev
 help / color / mirror / Atom feed
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: Mon, 13 Apr 2026 17:39:03 -0700	[thread overview]
Message-ID: <20260414003904.83824-1-sj@kernel.org> (raw)
In-Reply-To: <20260413184845.5130-1-aethernet65535@gmail.com>

On Tue, 14 Apr 2026 02:48:45 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:

> On Sun, 12 Apr 2026 14:37:19 -0700 SeongJae Park <sj@kernel.org> wrote:
> 
> > Hi Liew,
> > 
> > On Mon, 13 Apr 2026 03:04:55 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> > 
> > [...]
> > > > 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.
> 
> I've been thinking about what you meant by "make the desciption of the
> patch clear" for Series A.
> 
> Here's my current understanding:
> 
> "
> This patch only fixes the case where kdamond terminates because
> 'min_region_sz' is not power-of-2. Other causes of unexpected
> termination (e.g., memory allocation failures) are not fixed by this
> patch. [Seires B] will address the general problem.
> "
> 
> Is this what you had in mind? Or is there something else you think I
> should add or change?

To my understanding, you will make series B merged before this one, right?  If
that's the case, you may not need to add this description at all.  Rather, you
may better to clarify this is only a minor user experience improvement.

> 
> > 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.
> 
> Yes, I have enough capacity. My exams are not until a couple of weeks
> later, so I can focus on Series B now.
> 
> If my schedule gets too busy later, I will let you know and hand it over
> as you suggested. Thank you for offering that.

Sounds good.


Thanks,
SJ

[...]

  reply	other threads:[~2026-04-14  0:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  4:42 [PATCH v4 0/2] mm/damon: validate min_region_size to be power of 2 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
2026-04-13 18:48                   ` Liew Rui Yan
2026-04-14  0:39                     ` 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=20260414003904.83824-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