From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: sashiko-reviews@lists.linux.dev, Chris Mason <clm@fb.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-scsi@vger.kernel.org, ksummit@lists.linux.dev,
workflows@vger.kernel.org
Subject: Re: How to fix problems with the sashiko review model
Date: Wed, 22 Jul 2026 08:42:55 -0400 [thread overview]
Message-ID: <560cc442f7ff3dc1958da472f6a6ff2b357e2da2.camel@HansenPartnership.com> (raw)
In-Reply-To: <20260722121135.GB629472@killaraus.ideasonboard.com>
On Wed, 2026-07-22 at 15:11 +0300, Laurent Pinchart wrote:
> On Wed, Jul 22, 2026 at 07:58:48AM -0400, James Bottomley wrote:
> > There doesn't seem to be a Sashiko list, so I added ksummit as the
> > most likely one to catch attention. We got this review in SCSI on
> > this thread:
>
> workflows@vger.kernel.org seems a good candidate for discussions
> about tooling. The mailing list was created to share workflows and
> tools between maintainers as far as I understand.
Happy to keep this list cc'd, but I note I'm not on it so I'm not sure
how many other maintainers would be and the object is to engage driver
maintainer feedback on the proposal.
Regards,
James
next prev parent reply other threads:[~2026-07-22 12:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 4:12 [PATCH] scsi: mpt3sas: validate variable event array spans Pengpeng Hou
2026-07-22 4:27 ` sashiko-bot
2026-07-22 11:58 ` How to fix problems with the sashiko review model James Bottomley
2026-07-22 12:11 ` Laurent Pinchart
2026-07-22 12:42 ` James Bottomley [this message]
2026-07-22 13:08 ` Greg KH
2026-07-22 13:10 ` Greg KH
2026-07-22 13:45 ` James Bottomley
2026-07-22 14:08 ` Theodore Tso
2026-07-22 15:29 ` Miguel Ojeda
2026-07-22 13:42 ` James Bottomley
2026-07-22 14:00 ` Johannes Berg
2026-07-22 14:17 ` James Bottomley
2026-07-22 14:25 ` Johannes Berg
2026-07-22 15:39 ` Steven Rostedt
2026-07-22 15:55 ` James Bottomley
2026-07-22 16:36 ` Johannes Berg
2026-07-22 15:09 ` Mauro Carvalho Chehab
2026-07-22 15:24 ` James Bottomley
2026-07-22 20:25 ` Mauro Carvalho Chehab
2026-07-22 14:20 ` Mark Brown
2026-07-22 13:43 ` Guenter Roeck
2026-07-22 15:10 ` James Bottomley
2026-07-22 15:41 ` Miguel Ojeda
2026-07-22 15:54 ` Arnaldo Carvalho de Melo
2026-07-22 16:40 ` Roman Gushchin
2026-07-22 15:55 ` Roman Gushchin
2026-07-22 11:32 ` [PATCH] scsi: mpt3sas: validate variable event array spans James Bottomley
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=560cc442f7ff3dc1958da472f6a6ff2b357e2da2.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=clm@fb.com \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-scsi@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=workflows@vger.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