From: "Michael S. Tsirkin" <mst@redhat.com>
Cc: sashiko-reviews@lists.linux.dev, Chris Mason <clm@fb.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
virtualization@lists.linux-foundation.org,
ksummit@lists.linux.dev
Subject: How is sashiko bot deciding whom to Cc?
Date: Mon, 7 Sep 2026 06:03:39 -0400 [thread overview]
Message-ID: <20260907055646-mutt-send-email-mst@kernel.org> (raw)
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
next reply other threads:[~2026-09-07 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 10:03 Michael S. Tsirkin [this message]
2026-09-07 10:11 ` How is sashiko bot deciding whom to Cc? Wolfram Sang
2026-09-07 10:25 ` Michael S. Tsirkin
2026-09-07 11:25 ` Matthieu Baerts
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=20260907055646-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=clm@fb.com \
--cc=ksummit@lists.linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux-foundation.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