From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: (sashiko status) [PATCH 0/3] mm/damon: non-hotfix reviewed patches in damon/next tree
Date: Thu, 2 Apr 2026 17:27:19 -0700 [thread overview]
Message-ID: <20260403002720.46601-1-sj@kernel.org> (raw)
In-Reply-To: <20260402155733.77050-1-sj@kernel.org>
Dropping recipients who are not 100% surely interested in the sashiko review.
TL; DR: no blocker for this series is found.
Forwarding sashiko.dev review status for this series in a reply format with my
inline comments for details of why I say the TL; DR.
> # review url: https://sashiko.dev/#/patchset/20260402155733.77050-1-sj@kernel.org
>
> - [PATCH 1/3] mm/damon/ops-common: optimize damon_hot_score() using ilog2()
> - status: Reviewed
> - review: ISSUES MAY FOUND
No real issues here. Read my reply to the patch for more details.
> - [PATCH 2/3] Docs/admin-guide/mm/damon: fix 'parametrs' typo
> - status: Reviewed
> - review: No issues found.
As the 'review' is saying.
> - [PATCH 3/3] mm/damon: add synchronous commit for commit_inputs
> - status: Reviewed
> - review: ISSUES MAY FOUND
No real issues here. Read my reply to the patch for more details.
Thanks,
SJ
prev parent reply other threads:[~2026-04-03 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 15:57 [PATCH 0/3] mm/damon: non-hotfix reviewed patches in damon/next tree SeongJae Park
2026-04-02 15:57 ` [PATCH 1/3] mm/damon/ops-common: optimize damon_hot_score() using ilog2() SeongJae Park
2026-04-03 0:16 ` (sashiko review) " SeongJae Park
2026-04-02 15:57 ` [PATCH 2/3] Docs/admin-guide/mm/damon: fix 'parametrs' typo SeongJae Park
2026-04-02 15:57 ` [PATCH 3/3] mm/damon: add synchronous commit for commit_inputs SeongJae Park
2026-04-03 0:23 ` SeongJae Park
2026-04-03 0:27 ` 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=20260403002720.46601-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.