DAMON development mailing list
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Cheng Nie <niecheng1@uniontech.com>,
	shuah@kernel.org, damon@lists.linux.dev, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v4 0/2] selftests/damon: fix memcg_path staging handling
Date: Tue,  2 Jun 2026 22:04:26 -0700	[thread overview]
Message-ID: <20260603050427.91866-1-sj@kernel.org> (raw)
In-Reply-To: <20260601145501.116884-1-sj@kernel.org>

On Mon,  1 Jun 2026 07:55:00 -0700 SeongJae Park <sj@kernel.org> wrote:

> On Mon,  1 Jun 2026 17:01:19 +0800 Cheng Nie <niecheng1@uniontech.com> wrote:
> 
> Having a sentence for the cover letter would be nice.  E.g.,
> 
> '''
> Fix a bug in _damon_sysfs.py for damos_filter memcg_path setup, and add a test
> case of it in sysfs.py.
> '''
> 
> > Changes from v3:
> > - call stop() for cleanup without checking its return value
> > 
> > Changes from v2:
> > - configure memcg filter before start(), remove commit(), ignore
> >   start() failure, verify memcg_path staging readback only
> > - use print-style error messages as suggested
> > 
> > Cheng Nie (2):
> >   selftests/damon/_damon_sysfs.py: fix memcg_path assignment
> >   selftests/damon/sysfs.py: validate memcg_path staging readback
> 
> From the next time, please add links to the previous revisions [1].
> 
> For other readers,
> v3: https://lore.kernel.org/E4B88E7D4879D1B1+20260601074250.203583-1-niecheng1@uniontech.com
> v2: https://lore.kernel.org/4CDA28DC581FDCF8+20260529090845.1696845-1-niecheng1@uniontech.com
> v1: https://lore.kernel.org/406BD1BA0F6AE326+20260528081039.1192194-3-niecheng1@uniontech.com
> 
> I applied this series with the cover letter sentence change to damon/next [2]
> tree.  If this patch is not added to mm.git in short term (~1 week?), I will
> ask mm.git maintainer (Andrew Morton) to pick this.
> 
> Andrew might want us to repost this series after next rc1, though, as we are
> apparently wanting to make mm.git more stabilized at this point.  Andrew, pleae
> let me know if so.

Apparently that's the case.  That is, we are now quite close to next merge
window.  We want to focus on making mm.git more stabilized and therefore ready
for the next merge window, rather than adding more changes that no really
urgent.  I understand this series is not really urgent.  Hence, I will request
adding this to mm.git after next -rc1 release.  Let me know if you think this
is really  urgent.


Thanks,
SJ

[...]

      reply	other threads:[~2026-06-03  5:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  9:01 [PATCH v4 0/2] selftests/damon: fix memcg_path staging handling Cheng Nie
2026-06-01  9:05 ` [PATCH v4 1/2] selftests/damon/_damon_sysfs.py: fix memcg_path assignment Cheng Nie
2026-06-01  9:06 ` [PATCH v4 2/2] selftests/damon/sysfs.py: validate memcg_path staging readback Cheng Nie
2026-06-01 14:39   ` SeongJae Park
2026-06-01 14:55 ` [PATCH v4 0/2] selftests/damon: fix memcg_path staging handling SeongJae Park
2026-06-03  5:04   ` SeongJae Park [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=20260603050427.91866-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=niecheng1@uniontech.com \
    --cc=shuah@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