All of lore.kernel.org
 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: sashiko-bot@kernel.org's Cc list on reviews
Date: Mon, 18 May 2026 14:08:39 -0700	[thread overview]
Message-ID: <agt_1yfdx3YmjYei@google.com> (raw)

Hey Roman!

Sashiko's choice of Cc is... odd.  The original mail has a whole pile of folks
in both the To: and Cc:, but sashiko-bot is only replying to myself and (very
bizarrely) linux-hyperv@vger.kernel.org.

Oooh, is it perhaps because linux-hyperv@vger.kernel.org is the only mailing
list on the original Cc that has opted-in to getting emails?  If that's the case,
we might want to change that, even though it could result in people getting grumpy
about unwanted bot mail, because IMO the alternative is worse.  I've been responding
to some (mostly very good!) good sashiko-bot feedback, but only just now noticed
that the vast majority of folks on the To/Cc of the original patch won't see the
reviews.  That's bound to cause confusion, e.g. if someone reports the same issues
and/or manually looks at sashiko.dev.

----- Forwarded message from sashiko-bot@kernel.org -----

Date: Fri, 15 May 2026 19:55:51 +0000
From: sashiko-bot@kernel.org
To: Sean Christopherson <seanjc@google.com>
Cc: linux-hyperv@vger.kernel.org
Subject: Re: [PATCH v3 36/41] x86/kvmclock: Get local APIC bus frequency from PV CPUID Timing Info

...

----- End forwarded message -----

             reply	other threads:[~2026-05-18 21:08 UTC|newest]

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