The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Roman Gushchin <kfree@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sashiko-bot@kernel.org's Cc list on reviews
Date: Mon, 18 May 2026 16:59:24 -0700	[thread overview]
Message-ID: <agun3LseAsc8bmnk@google.com> (raw)
In-Reply-To: <CADKH=+2sHHR8M5qjDdjt6CjKOwdte_p8w03V_-kF7P1NwK9E6g@mail.gmail.com>

On Mon, May 18, 2026, Roman Gushchin wrote:
> On Mon, May 18, 2026 at 3:26 PM Sean Christopherson <seanjc@google.com> wrote:
> > On Mon, May 18, 2026, Roman Gushchin wrote:
> > > On Mon, May 18, 2026 at 2:08 PM Sean Christopherson <seanjc@google.com> wrote:
> > > In any case, I'm relying on the corresponding maintainers' decision on how
> > > they want to configure Sashiko.
> >
> > What level of configurability does the parser have?  Specifically, can it key off
> > the Cc/To in addition to the list?  I ask because I really, really, want to enable
> > auto-mailing for at least KVM x86, but kvm@vger.kernel.org is wildly overloaded.
> > I could try and drive consensus across all 30+ maintainers, but if there's a way
> > to precisely enable it for just KVM x86...
> >
> > E.g. is there a way to do something like:
> >
> > [subsystems.kvm_x86]
> > lists = ["kvm@vger.kernel.org" && <email is To: seanjc@google.com>]
> > reply_all = true
> 
> No, currently it's only per-mailing list. I did not expect that it
> would be that contentious.

Before you go add more configuration goo on your end, let me see what the other
kvm@ maintainers think.  Maybe we'll get lucky and everyone is on-board already.

> Maybe it should be based on entries in the maintainers file instead.
> But even then, what if a sub-subsystem wants emails and the top-level
> subsystem maintainers are against it? Or if a patchset touches multiple
> subsystems.

Hmm, maybe use a page table walker approach, and only send emails if every node of
the tree says yes?  Only getting email some of the time would be pretty darn
annoying though :-/

> I mean if building a complex configuration system is the only way forward,
> ok, it's kinda silly, but why not.

s/kinda silly/flat out stupid, given how easy it is to filter/ignore email.

Crazy idea: as a stopgap, what if sashiko emails linux-kernel@vger.kernel.org if
the list hasn't opted-in?  It wouldn't be as good as getting mails sent directly
to me, but subscribing to and filtering linux-kernel@vger.kernel.org mails is very
doable.  And even without subscribing to linux-kernel@vger.kernel.org, for those
of us that heavily utilize b4, it would better than clicking through a web site.

  reply	other threads:[~2026-05-18 23:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 21:08 sashiko-bot@kernel.org's Cc list on reviews Sean Christopherson
2026-05-18 21:39 ` Roman Gushchin
2026-05-18 22:26   ` Sean Christopherson
2026-05-18 23:27     ` Roman Gushchin
2026-05-18 23:59       ` Sean Christopherson [this message]
2026-05-18 23:27     ` Sean Christopherson
2026-05-18 23:35       ` Roman Gushchin

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=agun3LseAsc8bmnk@google.com \
    --to=seanjc@google.com \
    --cc=kfree@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@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