From: SeongJae Park <sj@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"# 5 . 19 . x" <stable@vger.kernel.org>,
David Hildenbrand <david@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Roman Gushchin <roman.gushchin@linux.dev>
Subject: Re: (sashiko status) [PATCH 0/2] Docs/admin-guide/mm/damon: warn commit_inputs vs other params race
Date: Sun, 29 Mar 2026 12:32:26 -0700 [thread overview]
Message-ID: <20260329193226.59025-1-sj@kernel.org> (raw)
In-Reply-To: <2026032915-library-embolism-b48c@gregkh>
+ Roman for a case he has any opinion about my sashiko usage.
Hello Greg,
On Sun, 29 Mar 2026 20:05:53 +0200 Greg KH <gregkh@linuxfoundation.org> wrote:
> On Sun, Mar 29, 2026 at 08:49:16AM -0700, SeongJae Park wrote:
> > Forwarding sashiko.dev review status for this thread.
> >
> > # review url: https://sashiko.dev/#/patchset/20260329153052.46657-1-sj@kernel.org
>
> Why are you doing this? If we want to see the review, can't we just go
> and look at the tool itself?
We can. But it is bit cumbersome to opening web browser and moving my focus to
there. Reading everything on the mailing tool is easier for some people like
me. Like some test bots send reports are replying to patches, or we sometimes
forwarding bugzilla reports to mailing lists in a form of a plain text mail.
Secondly, I have to share my opinions about the reviews, as many times AI
reviews need human's opinions. There is no good way to do that on the web ui
of the tool (sashiko) for now, and I think this mail based flow is the best.
And anyway I'm supposed to share at least my review of AI reviews, in mm
community. If I ignore, I will only make Andrew have to reply asking that.
I used to share only my review of the AI reviews as replies, instead of
forwarding AI reviews and then replies to those. But it was
1. cumbersome for me (should summarize AI review and then my review; feeling
doing work twice), and
2. feeling not optimal at sharing all concerning comments with others. My
summary might miss some points of AI review but other reviewers might just
believe me and don't read the full review due to the additional web browser
opening work. Also some other reivewers might kindly review AI reviews
before I do, and save my (or their) time.
Hence I ended up to do this bit odd workflow: Forwarding the full AI review on
the mailing list first, then reply my responses.
> sending it back to all of us feels odd,
If this is polluting your inbox and/or distract you, I'm so sorry for that.
Please let me know if this is distracting you. Maybe I can filtering people
who don't want this kind of replies out of the recipients for the forwarding
mails. Or, if you have a suggestion about what need to be changed, please let
me know.
> especially when it is your own patches.
Unfortuantely sashiko cannot send email on its own (yet). So I'm doing that
until it can.
>
> confused,
I hope my above explanation helps you.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-03-29 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 15:30 [PATCH 0/2] Docs/admin-guide/mm/damon: warn commit_inputs vs other params race SeongJae Park
2026-03-29 15:30 ` [PATCH 1/2] Docs/admin-guide/mm/damon/reclaim: warn commit_inputs vs param updates race SeongJae Park
2026-03-29 15:49 ` (sashiko review) " SeongJae Park
2026-03-29 15:54 ` SeongJae Park
2026-03-29 15:30 ` [PATCH 2/2] Docs/admin-guide/mm/damon/lru_sort: " SeongJae Park
2026-03-29 15:49 ` (sashiko review) " SeongJae Park
2026-03-29 15:55 ` SeongJae Park
2026-03-29 15:49 ` (sashiko status) [PATCH 0/2] Docs/admin-guide/mm/damon: warn commit_inputs vs other params race SeongJae Park
2026-03-29 16:31 ` SeongJae Park
2026-03-29 18:05 ` Greg KH
2026-03-29 19:32 ` SeongJae Park [this message]
2026-03-30 5:47 ` Greg KH
2026-03-30 6:39 ` Andrew Morton
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=20260329193226.59025-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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