From: "Theodore Tso" <tytso@mit.edu>
To: Jiri Kosina <jikos@kernel.org>
Cc: ksummit@lists.linux.dev, sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Sat, 17 Oct 2026 14:02:53 -0400 [thread overview]
Message-ID: <atO3pCuUxI950ftN@mit.edu> (raw)
In-Reply-To: <nn69829p-nn62-ppn7-968q-64o246ss90or@xreary.bet>
On Sat, Oct 17, 2026 at 07:28:48PM -0500, Jiri Kosina wrote:
> I have just received a v1 to v11 patchset submission within roughly one
> day timeframe.
>
> Neither myself nor anyone else did comment with any review feedback,
> except for Sashiko. Which I believe is what triggered all the immediate
> resubmissions.
What some subsystem maintainers have requested is delay sashiko
reviews from being sent out by some fixed time, such as 24 hours.
One approach which might want to explore is an exponential backoff.
> 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.
It's not that hard for people to set up a local Sashiko. and then use
either an local LLM, or their own cloud-hosted AI tokens. Perhaps
that's something we can encourage.
- Ted
next prev parent reply other threads:[~2026-10-17 18:04 UTC|newest]
Thread overview: 7+ 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 [this message]
2026-10-17 18:20 ` Alexei Starovoitov
2026-10-17 18:38 ` Arnaldo Melo
2026-10-17 18:20 ` Linus Torvalds
2026-10-17 20:10 ` Roman Gushchin
2026-10-17 19:42 ` Andrew Lunn
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=atO3pCuUxI950ftN@mit.edu \
--to=tytso@mit.edu \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=sashiko@lists.linux.dev \
/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.