All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.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 09:41:59 -0400	[thread overview]
Message-ID: <20261018094159.09f9e99a@fedora> (raw)
In-Reply-To: <7ia47bjg141n.fsf@castle.c.googlers.com>

On Sat, 17 Oct 2026 20:10:44 +0000
Roman Gushchin <roman.gushchin@linux.dev> wrote:

> It sounds like maintainers have drastically different preferences here,
> so I guess a per-mailing list configuration is the only reasonable
> setup? I'm trying to be on a conservative side, so e.g. if there is no
> consensus between maintainers, I do not enable emails.

Right. I have no issue with spamming of sashiko and back. I use
patchwork which is pretty good at only giving me the last version of a
series. And if I see that sashiko made a comment, I would have them
address it before I begin to review the series. Until sashiko is done,
I don't care if they send 11 iterations in a day. It's 11 iterations I
can ignore. In fact, that means I can start looking at it sooner.

As for Andrew's point on testing. I would hope that they would have
tested before sending v1. But sashiko is good at finding things that
tests don't catch. So if they are just fixing sashiko comments, it may
be that their tests are not catching what sashiko is finding. As
sashiko finds new issues with pretty much every new version, I can see
them having to constantly send another version with new info from
sashiko.

-- Steve

  reply	other threads:[~2026-10-18 13:42 UTC|newest]

Thread overview: 13+ 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-17 18:20 ` Alexei Starovoitov
2026-10-17 18:38   ` Arnaldo Melo
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 [this message]
2026-10-18 18:41     ` Kees Cook
2026-10-18 18:58       ` Linus Torvalds
2026-10-17 19:42 ` Andrew Lunn
2026-10-18 11:54   ` Mark Brown
2026-10-18 16:48     ` Laurent Pinchart

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=20261018094159.09f9e99a@fedora \
    --to=rostedt@goodmis.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 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.