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 v3 1/2] mm/damon/lru_sort: validate min_region_size to be power of 2
Date: Sat, 4 Apr 2026 13:18:21 -0700 [thread overview]
Message-ID: <20260404201822.86511-1-sj@kernel.org> (raw)
In-Reply-To: <20260404090927.6055-1-aethernet65535@gmail.com>
On Sat, 4 Apr 2026 17:09:27 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> On Fri, 3 Apr 2026 08:55:29 -0700 SeongJae Park <sj@kernel.org> wrote:
>
> > I recently learned not everyone is interested [1] in sashiko review. So when
> > I sharing sashiko review, I now try to drop recipients who are not necessarily
> > interested in the review. My choices at the moment is the author of the patch,
> > maintainers of the subsystem, and the mailing lists of the subsystem.
> >
> > So if I was sharing this review, I would dropped stable@ and yanquanmin1@ from
> > the Cc list.
> >
> > Please consider doing similar when you share sashiko review.
> >
> > Everyone including myself is learning how to use sashiko well, so it could be
> > confusing. Sorry about that. I'm planning to make a guideline for sashiko
> > review usage in DAMON subsystem, and update hkml to embed it, hoping that to
> > help reducing some of the confusion.
>
> Thank you for the guidance, I will keep this in mind for future Sashiko
> review forwards.
No worry. I just pushed hkml change for this. The latest version of hkml will
add the guide to the forwarding mail draft and make the format easier to add
your inline comments together, by default like below:
$ hkml patch sashiko_dev 20260325013939.18167-1-aethernet65535@gmail.com --for_forwarding
Adding your opinion together with the sashiko review sharing
is a recommended practice for reducing traffic. Will you
do so? If so, I will adjust format to be easier for that
[Y/n]
# sashiko review suggestions
#
# 1. Consider reducing recipients. Maybe the author,
# maintainers, reviewers, and mailing list of the
# direct subsystem and parent susystem mailing lists
# could be a starting point.
# 2. Add short summary of your opinion at the beginning.
# For example:
#
# sashiko found an issue. I will respin this patch.
# sashiko found no issue.
#
# Please don't forget removing this comment block before
# sending this!
Forwarding sashiko review in a reply format with my inline
comments below, for details of my view and doing discussions
via mails if needed.
> # review url: https://sashiko.dev/#/patchset/20260325013939.18167-1-aethernet65535@gmail.com
> # start of sashiko.dev inline review
> commit 60ccea4154b0c58741fae2323454a5a9496b67fa
> Author: Liew Rui Yan <aethernet65535@gmail.com>
[...]
>
> > Anyway, seems sashiko found no blockers for this patch.
>
> And thank you very much for reviewing the review! :>
I'm happy to help :)
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-04-04 20:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 5:23 [PATCH v3 0/2] mm/damon: validate min_region_size to be power of 2 Liew Rui Yan
2026-04-03 5:23 ` [PATCH v3 1/2] mm/damon/lru_sort: " Liew Rui Yan
2026-04-03 8:31 ` (sashiko review) " Liew Rui Yan
2026-04-03 15:55 ` SeongJae Park
2026-04-04 9:09 ` Liew Rui Yan
2026-04-04 20:18 ` SeongJae Park [this message]
2026-04-03 8:59 ` Quanmin Yan
2026-04-03 9:50 ` Liew Rui Yan
2026-04-03 16:19 ` SeongJae Park
2026-04-04 9:11 ` Liew Rui Yan
2026-04-04 20:30 ` SeongJae Park
2026-04-06 9:41 ` Liew Rui Yan
2026-04-06 15:50 ` SeongJae Park
2026-04-03 5:23 ` [PATCH v3 2/2] mm/damon/reclaim: " Liew Rui Yan
2026-04-03 8:33 ` (sashiko review) " Liew Rui Yan
2026-04-03 16:07 ` SeongJae Park
2026-04-03 16:20 ` 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=20260404201822.86511-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