How is sashiko bot deciding whom to Cc?

How is sashiko bot deciding whom to Cc?

[Michael S. Tsirkin]

There doesn't seem to be a Sashiko list, so I added ksummit as the most
likely one to catch attention. 

If you run b4 mbox  20260905153514.B55561F00A3A@smtp.kernel.org 
you will observe:

From: Karl Mehltretter <kmehltretter@gmail.com>
Date: Sat,  5 Sep 2026 17:20:59 +0200
To: "Michael S . Tsirkin" <mst@redhat.com>, Jason Wang <jasowangio@gmail.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: Karl Mehltretter <kmehltretter@gmail.com>, Xuan Zhuo <xuanzhuo@linux.alibaba.com>, Eugenio Pérez <eperezma@redhat.com>, Dmitry
        Torokhov <dmitry.torokhov@gmail.com>, Rusty Russell <rusty@rustcorp.com.au>, Pawel Moll <pawel.moll@arm.com>, Cornelia Huck
        <cohuck@redhat.com>, Halil Pasic <pasic@linux.ibm.com>, Eric Farman <farman@linux.ibm.com>, Richard Weinberger <richard@nod.at>,
        Anton Ivanov <anton.ivanov@cambridgegreys.com>, Johannes Berg <johannes@sipsolutions.net>, Hans de Goede <hansg@kernel.org>,
        Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>, Vadim Pasternak <vadimp@nvidia.com>, Bjorn Andersson <andersson@kernel.org>,
        Mathieu Poirier <mathieu.poirier@linaro.org>, virtualization@lists.linux.dev, linux-input@vger.kernel.org,
        linux-s390@vger.kernel.org, kvm@vger.kernel.org, linux-um@lists.infradead.org, platform-driver-x86@vger.kernel.org,
        linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/3] virtio: implement synchronize_cbs for remaining transports
Message-Id: <20260905152059.89560-4-kmehltretter@gmail.com>
In-Reply-To: <20260905152059.89560-1-kmehltretter@gmail.com>

with this diffstat:
---
 arch/um/drivers/virtio_uml.c             | 10 ++++++++++
 drivers/platform/mellanox/mlxbf-tmfifo.c | 14 ++++++++++++++
 drivers/remoteproc/remoteproc_core.c     | 10 ++++++++++
 drivers/remoteproc/remoteproc_virtio.c   | 20 +++++++++++++++++---
 drivers/virtio/virtio_vdpa.c             | 21 ++++++++++++++++++++-
 include/linux/remoteproc.h               |  3 +++



the sashiko bot replied to it:

From: sashiko-bot@kernel.org
Date: Sat, 05 Sep 2026 15:35:14 +0000
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>, Alexander Gordeev <agordeev@linux.ibm.com>,
        Christian Borntraeger <borntraeger@linux.ibm.com>, linux-input@vger.kernel.org, dmitry.torokhov@gmail.com, Vasily Gorbik
        <gor@linux.ibm.com>
Reply-To: sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH v2 3/3] virtio: implement synchronize_cbs for remaining transports
In-Reply-To: <20260905152059.89560-4-kmehltretter@gmail.com>
Message-Id: <20260905153514.B55561F00A3A@smtp.kernel.org>


So it picked some mailing lists but not others, and some specific people.

Is that opt-in somehow? I'll be happy to get Cc'd on the auto-review email.

-- 
James

Re: How is sashiko bot deciding whom to Cc?

[Wolfram Sang]

[-- Attachment #1: Type: text/plain, Size: 327 bytes --]


> So it picked some mailing lists but not others, and some specific people.
> 
> Is that opt-in somehow? I'll be happy to get Cc'd on the auto-review email.

To get me CCed with Renesas specific topics I sent a PR to modify this
file:

https://github.com/sashiko-dev/sashiko/blob/main/sashiko.dev/email_policy.toml


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: How is sashiko bot deciding whom to Cc?

[Michael S. Tsirkin]

On Mon, Sep 07, 2026 at 12:11:17PM +0200, Wolfram Sang wrote:
> 
> > So it picked some mailing lists but not others, and some specific people.
> > 
> > Is that opt-in somehow? I'll be happy to get Cc'd on the auto-review email.
> 
> To get me CCed with Renesas specific topics I sent a PR to modify this
> file:
> 
> https://github.com/sashiko-dev/sashiko/blob/main/sashiko.dev/email_policy.toml
> 

Got it, thanks! Sent a PR.

-- 
MST

Re: How is sashiko bot deciding whom to Cc?

[Matthieu Baerts]

Hello,

On 07/09/2026 12:03, Michael S. Tsirkin wrote:
> There doesn't seem to be a Sashiko list, so I added ksummit as the most
> likely one to catch attention.

Just in case, there is a Sashiko ML: sashiko@lists.linux.dev

https://subspace.kernel.org/lists.linux.dev.html

Cheers,
Matt