All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: sashiko@lists.linux.dev,  Christoph Hellwig <hch@lst.de>,
	 "Darrick J. Wong" <djwong@kernel.org>
Subject: Re: Full subsystem codebase scan for identifying pre-existing issues?
Date: Mon, 17 Aug 2026 20:15:27 +0000	[thread overview]
Message-ID: <7ia4y0e4ec68.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <CAJnrk1Y6twWcXfFesbLMNfMavg5RWgQ07pGJ1BM98V4o+FYcBw@mail.gmail.com> (Joanne Koong's message of "Wed, 29 Jul 2026 13:34:10 -0700")

Joanne Koong <joannelkoong@gmail.com> writes:

> Hi,

Hi Joanne!

> Is there a way for Sashiko to run a full scan of a subsystem/tree to
> identify all the pre-existing issues so that they can be fixed
> proactively? Currently, they're flagged on patch reviews, which can be
> a bit frustrating for contributors who didn't introduce the problem,
> and adds a bit of noise for maintainers/reviewers looking at the
> Sashiko report.

Well, I doubt there is a completely non-frustrating path here and the
current way of doing things is clearly working in a sense that there are
over 1000 upstream fixes now mentioning Sashiko. Somebody needs to spend
time on these findings and nobody obviously has this time freely
available.

That said, as Chris said, we're working on a more systematic way to
handle these findings, I hope to roll it out relatively soon.

Thanks

      parent reply	other threads:[~2026-08-17 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 20:34 Full subsystem codebase scan for identifying pre-existing issues? Joanne Koong
2026-07-30  1:43 ` Derek Barbosa
2026-07-30  2:01   ` Andrew Morton
2026-08-17 20:12     ` Roman Gushchin
2026-07-30 11:20   ` Chris Mason
2026-07-31  0:34   ` Joanne Koong
2026-07-31 12:29     ` Derek Barbosa
2026-08-17 20:18     ` Roman Gushchin
2026-08-17 20:15 ` Roman Gushchin [this message]

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=7ia4y0e4ec68.fsf@castle.c.googlers.com \
    --to=roman.gushchin@linux.dev \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=joannelkoong@gmail.com \
    --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.