From: Lorenzo Stoakes <ljs@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Lian Wang <lianux.mm@gmail.com>,
damon@lists.linux.dev, linux-mm@kvack.org,
daichaobing@sangfor.com.cn, kunwu.chan@gmail.com,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND RFC PATCH v2 0/5] mm/damon: add mTHP collapse and split actions
Date: Mon, 6 Jul 2026 12:59:12 +0100 [thread overview]
Message-ID: <akuYh9HQerTfUo1u@lucifer> (raw)
In-Reply-To: <20260703190421.100480-1-sj@kernel.org>
On Fri, Jul 03, 2026 at 12:04:20PM -0700, SJ Park wrote:
> On Thu, 2 Jul 2026 09:52:34 -0700 SJ Park <sj@kernel.org> wrote:
>
> > On Thu, 2 Jul 2026 11:23:55 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:
> >
> > > +cc all those you missed.
> >
> > Thank you for doing this, Lorenzo.
> >
> > >
> > > I really need to write a bot to do this, because I'm getting a little tired of
> > > pointing this out :))
> >
> > Good idea. I will also consider implementing this kind of checks to to my lzy
> > tool box [1] or hkml [2].
>
> I implemented [1] the check logic on hkml. Many things to fix and improve in
> future, but seems working at least for this series. You can use it like below:
>
> $ hkml patch check --check_recipients only ./0002-mm-khugepaged-add-damon-collapse-folio-range-for-external-callers.patch
> MISSING RECIPIENTS for [RESEND RFC PATCH v2 2/5] mm/khugepaged: add damon_collapse_folio_range() for external callers
> - Andrew Morton <akpm@linux-foundation.org>
> - David Hildenbrand <david@kernel.org>
> - Lorenzo Stoakes <ljs@kernel.org>
> - Zi Yan <ziy@nvidia.com>
> - Baolin Wang <baolin.wang@linux.alibaba.com>
> - "Liam R. Howlett" <liam@infradead.org>
> - Nico Pache <npache@redhat.com>
> - Ryan Roberts <ryan.roberts@arm.com>
> - Dev Jain <dev.jain@arm.com>
> - Barry Song <baohua@kernel.org>
> - Lance Yang <lance.yang@linux.dev>
> - Usama Arif <usama.arif@linux.dev>
> - linux-kernel@vger.kernel.org
> $ hkml patch check --check_recipients only ./0003-mm-damon-vaddr-implement-mthp-aware-damos-collapse-handler.patch
> MISSING RECIPIENTS for [RESEND RFC PATCH v2 3/5] mm/damon/vaddr: implement mTHP-aware DAMOS_COLLAPSE handler
> - Andrew Morton <akpm@linux-foundation.org>
> - linux-kernel@vger.kernel.org
>
> It is also integrated with the interactive mails list [2], so that you can run
> it without manually downloading the patch files.
>
> FWIW, 'hkml patch format' automatically adds recipients based on
> get_maintainer.pl, so this check is unnecessary for hkml users. But this will
> help me reviewing patches that not formatted with hkml or other similar
> scripts.
>
> hkml has a feature [3] to monitor new mails. Extending it to run this new
> check and send mails for check failures could be one of the ways to implement
> the bot. I'm not planning to do that by myself, though. I will run the check
> only for patches that look interesting to me, for now.
>
> [1] https://github.com/sjp38/hackermail/commit/9ca6fa1f71edc7a219edeb41d4c7f91
> [2] https://github.com/sjp38/hackermail/blob/master/USAGE.md#interactive-viewer
> [3] https://github.com/sjp38/hackermail/blob/master/USAGE.md#monitoring-mails
>
>
> Thanks,
> SJ
>
> [...]
Nice, thanks SJ! That's cool :)
Cheers, Lorenzo
next prev parent reply other threads:[~2026-07-06 11:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:46 [RESEND RFC PATCH v2 0/5] mm/damon: add mTHP collapse and split actions Lian Wang
2026-07-02 9:46 ` [RESEND RFC PATCH v2 1/5] mm/damon: add target_order field for DAMOS_COLLAPSE Lian Wang
2026-07-02 10:01 ` sashiko-bot
2026-07-02 18:51 ` SJ Park
2026-07-02 9:46 ` [RESEND RFC PATCH v2 2/5] mm/khugepaged: add damon_collapse_folio_range() for external callers Lian Wang
2026-07-02 10:13 ` sashiko-bot
2026-07-02 11:07 ` Lorenzo Stoakes
2026-07-02 19:43 ` SJ Park
2026-07-02 20:32 ` SJ Park
2026-07-02 9:46 ` [RESEND RFC PATCH v2 3/5] mm/damon/vaddr: implement mTHP-aware DAMOS_COLLAPSE handler Lian Wang
2026-07-02 10:26 ` sashiko-bot
2026-07-02 19:56 ` SJ Park
2026-07-02 9:46 ` [RESEND RFC PATCH v2 4/5] mm/damon: introduce DAMOS_SPLIT action Lian Wang
2026-07-02 10:41 ` sashiko-bot
2026-07-02 20:00 ` SJ Park
2026-07-02 9:46 ` [RESEND RFC PATCH v2 5/5] mm/damon/vaddr: implement DAMOS_SPLIT handler Lian Wang
2026-07-02 10:49 ` sashiko-bot
2026-07-02 20:18 ` SJ Park
2026-07-02 10:23 ` [RESEND RFC PATCH v2 0/5] mm/damon: add mTHP collapse and split actions Lorenzo Stoakes
2026-07-02 16:52 ` SJ Park
2026-07-03 19:04 ` SJ Park
2026-07-06 11:59 ` Lorenzo Stoakes [this message]
2026-07-03 1:35 ` wang lian
2026-07-02 18:35 ` SJ Park
2026-07-02 20:50 ` SJ Park
-- strict thread matches above, loose matches on Subject: below --
2026-07-02 9:52 Lian Wang
2026-07-02 16:39 ` SJ Park
[not found] <F1C05416-5D04-4568-B8CD-D4376B0F3848@gmail.com>
2026-07-03 16:37 ` SJ 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=akuYh9HQerTfUo1u@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=daichaobing@sangfor.com.cn \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=kunwu.chan@gmail.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=lianux.mm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=sj@kernel.org \
--cc=ziy@nvidia.com \
/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