From: Kees Cook <kees@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Kosina <jikos@kernel.org>,
ksummit@lists.linux.dev, sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Sun, 18 Oct 2026 11:41:49 -0700 [thread overview]
Message-ID: <202610181138.E3AC979EF@keescook> (raw)
In-Reply-To: <7ia47bjg141n.fsf@castle.c.googlers.com>
On Sat, Oct 17, 2026 at 08:10:44PM +0000, Roman Gushchin wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
> > On Sat, 17 Oct 2026 at 07:39, Jiri Kosina <jikos@kernel.org> wrote:
> >>
> >> Another option I'd like to propose would be to introduce a way for
> >> submitters to run patches through back-and-forth with Sashiko even before
> >> properly submitting the Sashiko-polished v1 to maintainers and
> >> mailinglists.
> >
> > I think maybe we should make it really easy for people to run their
> > some kind of sashiko setup on their own, rather than rely on sashiko
> > itself. After all, these are all people who use an LLM to begin with.
>
> It is really easy now:
> $ cargo install sashiko
> $ sashiko init
> set the LLM key
> $ cd linux && sashiko review HEAD^5..HEAD
FWIW, I have been using this for a while now (and making this "local
review" mode more ergonomic). With Anthropic's recent "API credit" stuff,
this works very well with the Haiku model (Opus is outrageous over-kill
and charges you 40x more than haiku).
--
Kees Cook
next prev parent reply other threads:[~2026-10-18 18:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 17:28 Patch pre-submission to Sashiko Jiri Kosina
2026-10-17 18:02 ` Theodore Tso
2026-10-19 11:02 ` johannes.goede
2026-10-19 20:27 ` Theodore Tso
2026-10-20 14:20 ` Bart Van Assche
2026-10-20 19:21 ` Theodore Tso
2026-10-20 20:15 ` Miguel Ojeda
2026-10-20 20:43 ` Shuah Khan
2026-10-21 11:07 ` Mark Brown
2026-10-21 16:20 ` Theodore Tso
2026-10-21 16:33 ` Mark Brown
2026-10-21 18:45 ` Andrew Morton
2026-10-21 19:15 ` Rafael J. Wysocki (Intel)
2026-10-21 19:56 ` Theodore Tso
2026-10-21 20:10 ` Jiri Kosina
2026-10-21 20:24 ` Steven Rostedt
2026-10-21 20:46 ` Paul E. McKenney
2026-10-17 18:20 ` Alexei Starovoitov
2026-10-17 18:38 ` Arnaldo Melo
2026-10-19 7:02 ` Dan Carpenter
2026-10-18 11:46 ` Mark Brown
2026-10-17 18:20 ` Linus Torvalds
2026-10-17 20:10 ` Roman Gushchin
2026-10-18 13:41 ` Steven Rostedt
2026-10-18 18:41 ` Kees Cook [this message]
2026-10-18 18:58 ` Linus Torvalds
2026-10-19 5:55 ` Oliver Slapinski
2026-10-17 19:42 ` Andrew Lunn
2026-10-18 11:54 ` Mark Brown
2026-10-18 16:48 ` Laurent Pinchart
2026-10-19 6:25 ` Krzysztof Kozlowski
2026-10-19 7:26 ` David Woodhouse
2026-10-19 11:40 ` Michal Simek
2026-10-19 12:02 ` Julia Lawall
2026-10-19 12:46 ` Michal Simek
2026-10-19 12:57 ` Julia Lawall
2026-10-19 17:30 ` Rodrigo Vivi
2026-10-19 17:53 ` Shuah Khan
2026-10-19 18:17 ` Arnaldo Melo
2026-10-19 20:35 ` Theodore Tso
2026-10-20 2:28 ` Chen-Yu Tsai
2026-10-20 8:36 ` Jiri Kosina
2026-10-20 8:48 ` Vlastimil Babka (SUSE)
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=202610181138.E3AC979EF@keescook \
--to=kees@kernel.org \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=sashiko@lists.linux.dev \
--cc=torvalds@linux-foundation.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