From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Jiri Kosina <jikos@kernel.org>, Theodore Tso <tytso@mit.edu>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
ksummit@lists.linux.dev, sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Tue, 20 Oct 2026 10:48:18 +0200 [thread overview]
Message-ID: <25fbde64-df97-4daf-aaef-5d2e6200044d@kernel.org> (raw)
In-Reply-To: <51o8r2nr-s30s-q915-58q2-2q4nr08006ns@xreary.bet>
On 10/20/26 10:36, Jiri Kosina wrote:
> On Mon, 19 Oct 2026, Theodore Tso wrote:
>
>> > When a submitter uses LLMs to generate a patch, it is reasonable for
>> > maintainers and reviewers to ask them to use shashiko to find problems
>> > before sending it to us. Asking for a shashkiko run before submitting
>> > patches could become part of the patch submitting process.
>> >
>> > How about updating the submitting patches document to add a section on
>> > this with instructions on how to run it?
>> >
>> > This shifts the responsibility to run shashiko to people using LLMs.
>>
>> If people are using LLM's to generate a patch, it would be useful if
>> we can make it super easy for LLM's to call out to Sashiko as an
>> sub-agent.
>
> Yeah, but that pretty much brings us back to the potentially problematic
> "free tokens for anybody developing out-of-tree / proprietary kernel code"
> territory again.
I assumed Ted meant to call out to a local sashiko (as Roman explained,
using the LLM itself), not the hosted one?
prev parent reply other threads:[~2026-10-20 8:48 UTC|newest]
Thread overview: 34+ 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-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
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) [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=25fbde64-df97-4daf-aaef-5d2e6200044d@kernel.org \
--to=vbabka@kernel.org \
--cc=jikos@kernel.org \
--cc=krzk@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=sashiko@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
/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