From: SJ Park <sj@kernel.org>
To: Hari Mishal <harimishal1@gmail.com>
Cc: SJ Park <sj@kernel.org>, Shuah Khan <shuah@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests/damon/sysfs.py: clean up sh processes used for obsolete_target test
Date: Wed, 22 Jul 2026 17:22:38 -0700 [thread overview]
Message-ID: <20260723002239.95987-1-sj@kernel.org> (raw)
In-Reply-To: <CAMmC+=BDZ6thHptTq=yGvfygUQb+0i2QeGbKXH+OFcXpnTXv1A@mail.gmail.com>
On Wed, 22 Jul 2026 21:15:56 +0200 Hari Mishal <harimishal1@gmail.com> wrote:
[...]
> > We (mm community) now want to focus on making mm.git more stabilized and
> > therefore ready for the next merge window, rather than adding more changes that
> > are not really urgent. I agree and want to help [1] that. For the reason,
> > unless Andre pick this first, I will request adding this to mm.git only after
> > next -rc1 release. Let me know if you think this is really urgent.
> >
> > [1] https://lore.kernel.org/20260722133829.87607-1-sj@kernel.org
>
> Definitely don't think it's an urgent change. Anyone who is using a
> tool like damon would be able to debug this quite easily.
> Thanks for clarity, again.
Thank you for confirming, Hari!
>
> Accidentally dropped reply all AGAIN, sorry about this. Resending to
> make sure everything is public again.
No worry, we all make mistakes and learn from those :)
Thanks,
SJ
prev parent reply other threads:[~2026-07-23 0:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 19:04 [PATCH] selftests/damon/sysfs.py: clean up sh processes used for obsolete_target test Hari Mishal
2026-07-21 23:51 ` SJ Park
2026-07-22 1:23 ` [PATCH v2] " Hari Mishal
2026-07-22 3:38 ` SJ Park
2026-07-22 13:48 ` SJ Park
2026-07-22 19:15 ` Hari Mishal
2026-07-23 0:22 ` SJ 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=20260723002239.95987-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=harimishal1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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