public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: "Gary Guo" <gary@garyguo.net>
Cc: "John Hubbard" <jhubbard@nvidia.com>,
	 "Miguel Ojeda" <ojeda@kernel.org>,
	 "rust-for-linux@vger.kernel.org"
	<rust-for-linux@vger.kernel.org>,
	 "Alexandre Courbot" <acourbot@nvidia.com>,
	 "Zi Yan" <ziy@nvidia.com>,
	 "Andrew Morton" <akpm@linux-foundation.org>,
	 "Jason Gunthorpe" <jgg@nvidia.com>,
	 "Leon Romanovsky" <leonro@nvidia.com>,
	 "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Sashiko.dev for Rust for Linux
Date: Fri, 20 Mar 2026 14:09:33 -0700	[thread overview]
Message-ID: <87a4w2tdgy.fsf@linux.dev> (raw)
In-Reply-To: <DH7W8TLZAKUB.2E0Q2VS546HBS@garyguo.net> (Gary Guo's message of "Fri, 20 Mar 2026 20:32:10 +0000")

"Gary Guo" <gary@garyguo.net> writes:

> On Fri Mar 20, 2026 at 8:24 PM GMT, Roman Gushchin wrote:
>> John Hubbard <jhubbard@nvidia.com> writes:
>>
>>> Hi Roman, Miguel,
>>
>> Hi John!
>>
>>> I was delighted with sashiko.dev after just a very quick peek at a
>>> few of its linux-mm reviews. Up until now, the AI code reviewers
>>> have often fixated on trivia, but this one goes right to real
>>> issues that actually matter. Sweeeet!
>>
>> Thank you!
>>
>>> So what would it take to get similar results for Rust for Linux?
>>> (A bunch of us are working on drivers/gpu/nova-core and 
>>> drivers/gpu/drm/nova, which are written in Rust.)
>>>
>>> I'm guessing a combination of "add rust-for-linux to the list
>>> of mailing lists", and a whole bunch of new Rules/Skills?
>>
>> Yes, I'm going to add rust-for-linux (will appear ~tomorrow), but a
>> bunch of patchsets which cc'ed lkml have already been reviewed, please,
>> take a look.
>>
>> We don't need any rules/skills to get *some* reviews, but we certainly
>> might need some prompts to get *better* reviews, both in terms of bug
>> discovery and false positives. If you'll master something, I'm more than
>> happy to give it a try.
>>
>> Thanks,
>> Roman
>
> Hi Roman,
>
> First of all, great work. It has already produced useful review on my
> patchsets.

Thanks!

> I've seen a few false positives on Sashiko which seems to be that it understands
> the Rust code from an userspace Rust perspective and doesn't know some of our
> unique constructs (most notably, the way we handling bindings/FFI).

Yeah, I'd imagine that adding some rust-for-kernel prompts should help a lot.
>
> I'm preparing some prompt changes locally and am testing these out, to see if it
> reduces false positives. It appears to me that the prompt for Sashiko is from
> https://github.com/masoncl/review-prompts? If I made a PR there it would
> eventually land in Sashiko, too, right?

Yes, I'm using some prompts from Chris's repository, but not all of
them. We're in touch with Chris and thinking how to better share them.
As of now, anything works, send them either way, we'll figure out the
syncing part.

Thanks,
Roman


  reply	other threads:[~2026-03-20 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 19:40 Sashiko.dev for Rust for Linux John Hubbard
2026-03-20 20:24 ` Roman Gushchin
2026-03-20 20:32   ` Gary Guo
2026-03-20 21:09     ` Roman Gushchin [this message]
2026-03-21 13:33   ` Miguel Ojeda
2026-03-21 20:28 ` Danilo Krummrich

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=87a4w2tdgy.fsf@linux.dev \
    --to=roman.gushchin@linux.dev \
    --cc=acourbot@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=gary@garyguo.net \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=ziy@nvidia.com \
    /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