From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jiri Kosina <jikos@kernel.org>, ksummit@lists.linux.dev
Cc: sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Mon, 19 Oct 2026 08:25:03 +0200 [thread overview]
Message-ID: <350c7564-a833-4dd4-abf3-b8488280b0fa@kernel.org> (raw)
In-Reply-To: <nn69829p-nn62-ppn7-968q-64o246ss90or@xreary.bet>
On 17/10/2026 19:28, Jiri Kosina wrote:
>
> [ in the spirit of the concluding discussion at this year's maintainers
> summit, I'm using this list outside of actual maintainer summit
> planning :) ]
>
> 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.
>
> I don't think this is sustanable.
I think it might be fine to drop usual expectation of one patchset per
24h as long as maintainers can completely ignore patchsets with Sashiko
replies.
If people want to keep bouncing the ball between them and Sashiko, they
should be allowed and then we should be allowed just to silence that
email thread completely.
>
> The idea of throttling Sashiko's responses was gently nibbled at the
> summit, and might be one of the options how to deal with this.
>
> 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 assume you mean they will be running it through Sashiko
infrastructure, so using sponsored tokens. Otherwise that possibility is
already there - you can run Sashiko, just a matter of money.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-19 6:25 UTC|newest]
Thread overview: 35+ 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-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 [this message]
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=350c7564-a833-4dd4-abf3-b8488280b0fa@kernel.org \
--to=krzk@kernel.org \
--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.