From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"# 6 . 15 . x" <stable@vger.kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/damon/core: avoid use of half-online-committed context
Date: Sun, 22 Mar 2026 12:26:40 -0700 [thread overview]
Message-ID: <20260322192641.87848-1-sj@kernel.org> (raw)
In-Reply-To: <20260321021628.78887-1-sj@kernel.org>
On Fri, 20 Mar 2026 19:16:35 SeongJae Park <sj@kernel.org> wrote:
[...]
> By the way, I am also doing monitoring of sashiko.dev for all DAMON patches.
> It will be much easier once sashiko.dev's email feature is ready, since I
> already onboarded DAMON for that.
>
> Meanwhile, the monitoring using web browser is somewhat tedious for me, so I
> just implemented an hkml feature, namely
> 'hkml patch sashiko_dev --thread_status'. It receives a message id of a mail,
> and prints the review status/result of all patches of the thread.
>
> E.g.,
>
> $ hkml patch sashiko_dev --thread_status 20260319-memory-failure-mf-delayed-fix-rfc-v2-v2-0-92c596402a7a@google.com
> - [PATCH RFC v2 1/7] mm: memory_failure: Clarify the MF_DELAYED definition
> - Reviewed (Review completed successfully.)
> - [PATCH RFC v2 2/7] mm: memory_failure: Allow truncate_error_folio to return MF_DELAYED
> - Reviewed (Review completed successfully.)
> - [PATCH RFC v2 3/7] mm: shmem: Update shmem handler to the MF_DELAYED definition
> - Reviewed (Review completed successfully.)
> - [PATCH RFC v2 4/7] mm: memory_failure: Generalize extra_pins handling to all MF_DELAYED cases
> - Pending (None)
> - [PATCH RFC v2 4/7] mm: memory_failure: Generalize extra_pins handling to all MF_DELAYED cases
> - Reviewed (Review completed successfully.)
> - [PATCH RFC v2 5/7] mm: selftests: Add shmem memory failure test
> - Reviewed (Review completed successfully.)
> - [PATCH RFC v2 6/7] KVM: selftests: Add memory failure tests in guest_memfd_test
> - Reviewed (Review completed successfully.)
> - [PATCH RFC v2 7/7] KVM: selftests: Test guest_memfd behavior with respect to stage 2 page tables
> - Reviewed (Review completed successfully.)
>
> I'm planning to implement another feature for formatting and sending the review
> result and inline comments as emails, probably this weekend.
Now the feature is available on 'master' branch of hkml. I started using it
since yesterday for DAMON patches, and it works for at least my workflow. The
documentation is also updated [1].
[1] https://github.com/sjp38/hackermail/blob/test/USAGE.md#forwarding-sashikodev-statuscomments-to-mailing-list
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-03-22 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 14:52 [PATCH] mm/damon/core: avoid use of half-online-committed context SeongJae Park
2026-03-20 2:48 ` Andrew Morton
2026-03-20 3:15 ` SeongJae Park
2026-03-21 2:16 ` SeongJae Park
2026-03-21 2:25 ` SeongJae Park
2026-03-22 19:26 ` SeongJae Park [this message]
2026-03-22 19:32 ` 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=20260322192641.87848-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-mm@kvack.org \
--cc=stable@vger.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