All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Ways to handle Sashiko bug reports for DAMON (was "Re: [False Bug] mm/damon/core: uninitialized boolean fields in damon_new_scheme()")
Date: Sat, 24 Oct 2026 14:05:53 -0700	[thread overview]
Message-ID: <20261024210554.88440-1-sj@kernel.org> (raw)
In-Reply-To: <20261024195239.87431-1-sj@kernel.org>

On Sat, 24 Oct 2026 12:52:39 -0700 SJ Park <sj@kernel.org> wrote:

> Hello,
> 
> 
> Sashiko reported a bug that I believe a false positive.  Sharing the report and
> why I think it is false in usual mail format, to get help from more eyeballs.

I was about to keep doing this for all false positive reports.  I added a
comment on the Sashiko web ui for this report, closed it, and opened another
report that I think a false positive.  And I realized this is tedious and not
sustainable.

Actually nowadays I was taking time to think about more options.  Those include
but not limited to making more tooling and just sharing everything on the
mailing list and forget about the database.  I still find no best option.  And
I feel like I might spending too much time on this.

Maybe I'm thinking too much.  I will just do whatever I feel better to do at
the moment.  So I might share some Sashiko reports on mailing list or not.
Maybe I will start from just not sharing Sashiko reports on mailing list except
mentioning those on relevant patch descriptions including Closes: tag.  Please
don't expect any consistency in my way of Sashiko reports handling for now.


Thanks,
SJ

      reply	other threads:[~2026-10-24 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24 19:52 [False Bug] mm/damon/core: uninitialized boolean fields in damon_new_scheme() SJ Park
2026-10-24 21:05 ` SJ Park [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=20261024210554.88440-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@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.