From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Roman Gushchin <roman.gushchin@linux.dev>
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: Sat, 21 Mar 2026 14:33:49 +0100 [thread overview]
Message-ID: <CANiq72=HYHj4ZhFWqTJk3DhVEoOqFKah6yA9ROfC+Z797SwUZw@mail.gmail.com> (raw)
In-Reply-To: <87ldfmtfk7.fsf@linux.dev>
On Fri, Mar 20, 2026 at 9:24 PM Roman Gushchin <roman.gushchin@linux.dev> wrote:
>
> 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.
I see the list there:
https://sashiko.dev/#/?list=org.kernel.vger.rust-for-linux
I have just added a link to it from rust-for-linux.com (in the menu
bar, where I keep many links to resources etc.), and announced it in
our Zulip and the mailing list (I guess this thread is short enough
that could have served the purpose too).
> 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.
Yeah, we should definitely add some context (and possibly skills like
Coccinelle for Rust to match the recently merged Coccinelle one
eventually).
I see Gary already replied -- I was going to mention that he has been
playing around with it for some days indeed!
Thanks a lot!
Cheers,
Miguel
next prev parent reply other threads:[~2026-03-21 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 19:40 John Hubbard
2026-03-20 20:24 ` Roman Gushchin
2026-03-20 20:32 ` Gary Guo
2026-03-20 21:09 ` Roman Gushchin
2026-03-21 13:33 ` Miguel Ojeda [this message]
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='CANiq72=HYHj4ZhFWqTJk3DhVEoOqFKah6yA9ROfC+Z797SwUZw@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=acourbot@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=ojeda@kernel.org \
--cc=roman.gushchin@linux.dev \
--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