All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Theodore Tso <tytso@mit.edu>, johannes.goede@oss.qualcomm.com
Cc: Jiri Kosina <jikos@kernel.org>,
	ksummit@lists.linux.dev, sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Tue, 20 Oct 2026 07:20:53 -0700	[thread overview]
Message-ID: <2fef166e-088d-4ffe-8d0a-0143aebc1b26@acm.org> (raw)
In-Reply-To: <atZ4J86j7CXF82HX@mit.edu>

On 10/19/26 1:27 PM, Theodore Tso wrote:
> As someone else has pointed out, students / hobbyists just use
> OpenCode with the review prompts with one of their free models, such
> as "Big Pickle".  That or a local quen3-coder-next (my current local
> LLM, when I'm not using my employer's cloud hosted models) might not
> be as good as Sashiko, but you can find a lot of the obvious issues
> first, before you send it to the public list.

Does the requirement to run a local LLM raise the barrier to start with
kernel coding? The following approach is not as good as running Sashiko
locally but can help those who can't run an LLM locally:
* Open the website of your favorite LLM.
* Enter the prompt "Create a prompt for performing a Sashiko-style Linux 
kernel patch review. In this context Sashiko refers to 
https://github.com/sashiko-dev/sashiko"
* Copy/paste the generated prompt. Do not submit it yet.
* Copy/paste the patches that should be reviewed into the LLM web
   browser session, e.g. with git format-patch ...; cat *.patch | wl-copy
* Submit the review prompt + patches to the LLM and let the LLM review
   your code.

Bart.

  reply	other threads:[~2026-10-20 14:20 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 [this message]
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)

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=2fef166e-088d-4ffe-8d0a-0143aebc1b26@acm.org \
    --to=bvanassche@acm.org \
    --cc=jikos@kernel.org \
    --cc=johannes.goede@oss.qualcomm.com \
    --cc=ksummit@lists.linux.dev \
    --cc=sashiko@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.