From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Fengnan Chang <fengnanchang@gmail.com>
Subject: Re: Should we hook up sashiko.dev?
Date: Wed, 22 Apr 2026 07:35:17 -0400 [thread overview]
Message-ID: <aeiydeH-zDYw3yCK@bfoster> (raw)
In-Reply-To: <83e6b930-2705-4719-80cc-71987092f1b7@sandeen.net>
On Tue, Apr 21, 2026 at 06:47:01PM -0500, Eric Sandeen wrote:
> On 4/15/26 11:49 AM, Eric Sandeen wrote:
> > Hi all -
> >
> > "Sashiko is an agentic Linux kernel code review system. It monitors public mailing lists to thoroughly evaluate proposed Linux kernel changes. The system acts like a team of specialized reviewers covering domains from high-level architecture verification and security audits to low-level resource management and concurrency analysis."
> >
> > This is something built by Chris Mason and others, with Google providing the LLM and tokens.
> >
> > The website sashiko.dev shows these review results for mailing lists it is subscribed to, so you can browse around and see how it works. I've heard reasonably positive feedback from some who've used it already.
> >
> > We could send a PR to request adding linux-xfs, and I think we should try it.
>
> Ok, we're connected: https://sashiko.dev/#/?list=org.kernel.vger.linux-xfs
>
> for now it is not sending any emails; it's web-only. Depending on the
> usefulness and accuracy of the reviews, we could consider more than web-only.
>
> I'd like to set up some xfs-specific review prompts, but apparently we need
> to be somewhat sparse on that due to token usage for a large set of prompts.
>
> LMK what you think of the review quality!
>
I just took a quick look at this one and it seems like it's accurate:
https://sashiko.dev/#/patchset/20260420061630.62077-1-changfengnan%40bytedance.com
The flaw isn't actually with the patch, but rather the surrounding code
it touches. It also feels a little weird to me to have a tool that tries
to communicate like a person, but maybe that's just something to get
used to I guess. ;)
Fengnan,
Any chance you want to try to fix that up in your patch, since it's
outstanding and you've created the helper to facilitate it? ;) If not
nbd we can fix it up separately. I don't think it's a pressing issue.
Brian
prev parent reply other threads:[~2026-04-22 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 16:49 Should we hook up sashiko.dev? Eric Sandeen
2026-04-15 18:40 ` Carlos Maiolino
2026-04-15 18:45 ` Eric Sandeen
2026-04-20 8:54 ` Andrey Albershteyn
2026-04-21 23:47 ` Eric Sandeen
2026-04-22 11:35 ` Brian Foster [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=aeiydeH-zDYw3yCK@bfoster \
--to=bfoster@redhat.com \
--cc=fengnanchang@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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