From: Oliver Upton <oupton@kernel.org>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Will Deacon <will@kernel.org>,
Vincent Donnefort <vdonnefort@google.com>,
KVMARM <kvmarm@lists.linux.dev>
Subject: Re: Sashiko review emails to the list
Date: Fri, 19 Jun 2026 09:45:25 -0700 [thread overview]
Message-ID: <ajVyJa-mZmYGzt6o@kernel.org> (raw)
In-Reply-To: <CA+EHjTzdCf2waY_Qc+GWzA-MuKG=_XjQ4Hzn3HJ6Yi0NfB_CzQ@mail.gmail.com>
Hey,
On Fri, Jun 19, 2026 at 03:19:05PM +0100, Fuad Tabba wrote:
> Hi folks,
>
> I really like Sashiko and find it very useful. It's flagged real bugs
> in series I and others have posted to the list (e.g. [1][2][3]), and I
> run it locally before sending, which has saved me a few respins.
>
> That said, it's been posting a lot lately, so it seemed worth asking
> how the review emails to the list are working out, and whether we
> should change anything.
So this is entirely my fault since I added the email configuration for
the kvmarm list. Sashiko has been finding some truly nasty bugs, posting
on-list is the easiest way to get attention from the right folks to get
things fixed.
With that being said, the signal to noise ratio hasn't been ideal.
> These fixes will take a while to land, so the question is what to do
> meanwhile. Some options, and surely others:
>
> - Leave it as-is while the fixes propagate.
> - Stop the emails but keep the reviews on sashiko.dev, so people can
> look rather than have them pushed.
> - Disable the emails until the noise is down to a reasonable level,
> then re-enable.
This sounds like the right approach. I'd like to re-enable emails once
we're happy with the quality of reviews.
On another note: Roman, is it possible to separately report pre-existing
issues from findings in a patch? Maintainers have a higher likelihood of
caring about these than individual contributors anyway.
Thanks,
Oliver
next prev parent reply other threads:[~2026-06-19 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 14:19 Sashiko review emails to the list Fuad Tabba
2026-06-19 16:45 ` Oliver Upton [this message]
2026-06-19 18:05 ` Roman Gushchin
2026-06-22 16:53 ` Oliver Upton
2026-06-22 19:20 ` Roman Gushchin
2026-06-23 0:21 ` Oliver Upton
2026-06-21 11:03 ` Marc Zyngier
2026-06-22 9:28 ` Fuad Tabba
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=ajVyJa-mZmYGzt6o@kernel.org \
--to=oupton@kernel.org \
--cc=fuad.tabba@linux.dev \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=vdonnefort@google.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox