From: SeongJae Park <sj@kernel.org>
To: "Theodore Tso" <tytso@mit.edu>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.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: Tue, 31 Mar 2026 08:55:06 -0700 [thread overview]
Message-ID: <20260331155507.79720-1-sj@kernel.org> (raw)
In-Reply-To: <20260331121943.GA74409@macsyma-wired.lan>
On Tue, 31 Mar 2026 08:19:43 -0400 "Theodore Tso" <tytso@mit.edu> wrote:
> On Mon, Mar 30, 2026 at 02:22:05PM -0700, Andrew Morton wrote:
> >
> > I view Sashiko as primarily an author tool. Sometimes I call it
> > checkpatch++. In a better world, author would be able to sort out
> > Sashiko issues before ever sending out the patchset. But in this
> > world, a public send is needed to obtain that review.
>
> Note that Sashiko is fully open source and the prompts are available
> in third_party/prompts in the git repo:
>
> https://github.com/sashiko-dev/sashiko
>
> So people can run it privately, although they will need to provide
> their own LLM credits.
That's unfortunately a barrier to some people. To me, what makes sashiko
special and different from other AI review tools is the fact that it is
automatically reviewing nearly every kernel patch for free and publicly sharing
the results.
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-03-31 15:55 UTC|newest]
Thread overview: 18+ 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
2026-03-30 5:47 ` Greg KH
2026-03-30 6:39 ` Andrew Morton
2026-03-31 4:34 ` SeongJae Park
2026-03-30 21:22 ` Andrew Morton
2026-03-31 4:52 ` SeongJae Park
2026-03-31 12:19 ` Theodore Tso
2026-03-31 15:55 ` 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=20260331155507.79720-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=tytso@mit.edu \
--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