Linux Trace Kernel
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Roman Gushchin <roman.gushchin@linux.dev>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Linux trace kernel <linux-trace-kernel@vger.kernel.org>
Subject: Re: Linking Patchwork with Sashiko?
Date: Tue, 21 Jul 2026 09:34:49 +0900	[thread overview]
Message-ID: <20260721093449.968265216a1201101383b443@kernel.org> (raw)
In-Reply-To: <20260720093655.4da2224d@robin>

On Mon, 20 Jul 2026 09:36:55 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> [ Removed all Cc's. Added Masami and linux-trace-kernel mailing list ]
> 
> On Thu, 16 Jul 2026 00:09:39 +0000
> Roman Gushchin <roman.gushchin@linux.dev> wrote:
> 
> > Steven Rostedt <rostedt@goodmis.org> writes:
> > 
> > > On Wed, 15 Jul 2026 21:08:47 +0000
> > > Roman Gushchin <roman.gushchin@linux.dev> wrote:
> > >  
> > >> At this moment there are 36 mailing lists who opted in for delivering email
> > >> reviews over email (without counting linux-media@). In every single case
> > >> it was based on maintainers requests in all cases of a disagreement
> > >> between maintainers I took the conservative side.  
> > >
> > > Oh, I think I missed this opt-in. Can you add replies to patches sent
> > > to linux-trace-kernel. Currently, I've been manually looking to see if
> > > a patch had a Sashiko review and sending the author a link to the
> > > review and told them to please reply to the comments.
> > >
> > > Note, I have not had anyone tell me the are against doing so.  
> > 
> > May I ask you to raise this question with other linux-trace-kernel
> > maintainers and cc me on the thread? Just to make sure everyone is
> > onboard.
> 
> Masami,
> 
> Are you OK with having Sashiko send an email on what it finds to the
> author and the mailing list?

Yeah, I hope that is good to make a discussion on ML about reviewed
result.
Mostly those are reasonable now, so maybe we need to decide a standard
format for "all-Ack".

Current problem is that the Sashiko does not look back the previous
discussion, so the commit or code comment should clearly state
"this code is intensionally do something."

A current issue is that, since Sashiko does not reflect the content
of past discussions, we must explicitly state within commits or code
comments, (where you have determined that a past review comment was
incorrect) that the code is intentionally doing this operation and why.

> > 
> > Also, please, let me know if sashiko should reply to the author and
> > also if it should send an email if there are no issues found.
> 
> I think if it finds no issues it should still send the email, as it
> adds to the confidence of the patch. It also lets us know that the
> email wasn't just dropped.
> 
> Oh, I would think that "Failed to apply" results should *not* be sent.

Yes, the fact that there is no response from Sashiko implies that
the application failed.

Thank you,

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2026-07-21  0:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260715005909.GF1656185@killaraus.ideasonboard.com>
     [not found] ` <4928C919-7999-4E76-ADCB-F8643FED105B@linux.dev>
     [not found]   ` <20260715162816.GF1778116@killaraus.ideasonboard.com>
     [not found]     ` <7ia47bmw0xls.fsf@castle.c.googlers.com>
     [not found]       ` <20260715192042.4052411a@robin>
     [not found]         ` <7ia4wluvvlq4.fsf@castle.c.googlers.com>
2026-07-20 13:36           ` Linking Patchwork with Sashiko? Steven Rostedt
2026-07-21  0:34             ` Masami Hiramatsu [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=20260721093449.968265216a1201101383b443@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=rostedt@goodmis.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