All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Greg KH <gregkh@linuxfoundation.org>,
	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
Subject: Re: How to fix problems with the sashiko review model
Date: Wed, 22 Jul 2026 12:54:59 -0300	[thread overview]
Message-ID: <amDn0zh-fsrlGLoD@x1> (raw)
In-Reply-To: <8cb7a4a8a13bb003daa1d1413517e104955772d3.camel@HansenPartnership.com>

On Wed, Jul 22, 2026 at 11:10:45AM -0400, James Bottomley wrote:
> On Wed, 2026-07-22 at 06:43 -0700, Guenter Roeck wrote:
> [...]
> > For Sashiko, fork and clone
> > https://github.com/sashiko-dev/sashiko.git,
> > submit your changes into the clone, and send a pull request. Or at
> > least that is how I do it.

> > In the Sashiko source, per-subsystem prompts are located in directory
> > third_party/prompts/kernel/subsystem.

> OK, now I'm confused.  I thought

> https://github.com/masoncl/review-prompts

> was the source of truth for this, but that project seems to have been
> copied into sashiko rather than pulled in as a module.  If you want to
> improve the review prompts do you now have to submit to both (which is
> getting to be a bit wasteful)?

My experience is you submit to Chris's and it eventually gets pulled
into Roman's:

June 12
prompts: sync recent changes from review-prompts
https://github.com/sashiko-dev/sashiko/commit/07223d03b2657d809156b46c0b980725184f81e8

But from what I saw while searching for the above commit there are
updates to prompts in sashiko, not going first thru review-prompts.

- Arnaldo

  parent reply	other threads:[~2026-07-22 15:55 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
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 [this message]
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=amDn0zh-fsrlGLoD@x1 \
    --to=acme@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=clm@fb.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=roman.gushchin@linux.dev \
    --cc=sashiko-reviews@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.