Sashiko discussions
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: SJ Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	sashiko@lists.linux.dev
Subject: Re: email handling
Date: Mon, 12 Oct 2026 15:11:28 -0700	[thread overview]
Message-ID: <20261012221129.375576-1-sj@kernel.org> (raw)
In-Reply-To: <6355837F-7F0E-4C49-B1D4-223296508C18@linux.dev>

On Mon, 12 Oct 2026 14:58:56 -0700 Roman Gushchin <roman.gushchin@linux.dev> wrote:

> 
> 
> > On Oct 12, 2026, at 2:25 PM, SJ Park <sj@kernel.org> wrote:
> > 
> > Hi Andrew,
> > 
> >> On Sat, 10 Oct 2026 15:06:29 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> >> 
> >> 
> >> Concerning this email:
> >>    https://lore.kernel.org/20261009-b4-mmap-prepare-vma-flag-sanify-v5-16-923b70125b1e@kernel.org
> >> 
> >> I discovered that some lucky duckies were receiving Sashiko emails:
> > 
> > Apparently that's because the patch is Cc-ing a few mailing lists that are
> > configured [1] to receive the review mails.  For example, the patch is Cc-ing
> > s390@ mailing list, and it is configured [2] to send the review email to the
> > author of the patch, the mailing list, and a few more people including Heiko.
> > To quote the config [2],
> > 
> >    ["linux-s390@vger.kernel.org"]
> >    reply_to = ["author", "list"]
> >    positive_review = "all"
> >    cc = ["Heiko Carstens <hca@linux.ibm.com>", "Vasily Gorbik <gor@linux.ibm.com>", "Alexander Gordeev <agordeev@linux.ibm.com>", "Christian Borntraeger <borntraeger@linux.ibm.com>"]
> > 
> >> 
> >> Subject: Re: [PATCH v5 16/38] mm/vma: add and use
> >> vma_[flags]_is_fixed_mapping
> >> Reply-To: sashiko-reviews@lists.linux.dev
> >> To: =?utf-8?b?TG9yZW56byBTdG9ha2VzIChBUk0p?= <ljs@kernel.org>
> >> Cc: linux-trace-kernel@vger.kernel.org, kvmarm@lists.linux.dev, "Vasily
> >> Gorbik" <gor@linux.ibm.com>, "Oliver Upton" <oupton@kernel.org>, "Heiko
> >> Carstens" <hca@linux.ibm.com>, linux-perf-users@vger.kernel.org, "Marc
> >> Zyngier" <maz@kernel.org>, "Alexander Gordeev" <agordeev@linux.ibm.com>, linux-scsi@vger.kernel.org, selinux@vger.kernel.org, "Christian
> >> Borntraeger" <borntraeger@linux.ibm.com>, bpf@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-rdma@vger.kernel.org, kvm@vger.kernel.org, linux-s390@vger.kernel.org, linux-usb@vger.kernel.org
> >> In-Reply-To: <20261009-b4-mmap-prepare-vma-flag-sanify-v5-16-923b70125b1e@kernel.org>
> >> References: <20261009-b4-mmap-prepare-vma-flag-sanify-v5-0-923b70125b1e@kernel.org>
> >> <20261009-b4-mmap-prepare-vma-flag-sanify-v5-16-923b70125b1e@kernel.org>
> >> 
> >> 
> >> 
> >> But I did not.  How come?  I was on the To: line so why were certain
> >> people emailed but not me?
> > 
> > I think that's because you are not on the configuration.
> > 
> >> 
> >> I'd prefer to receive such replies.
> > 
> > Maybe you could add below change to get replies for mm patches?
> > 
> >    diff --git a/projects/linux/mailing_lists.toml b/projects/linux/mailing_lists.toml
> >    index e41f1aa..330d1d8 100644
> >    --- a/projects/linux/mailing_lists.toml
> >    +++ b/projects/linux/mailing_lists.toml
> >    @@ -313,3 +313,6 @@ reply_to = ["author", "list", "recipients"]
> > 
> >     ["fsverity@lists.linux.dev"]
> >     reply_to = ["author", "list", "recipients"]
> >    +
> >    +["linux-mm@kvack.org"]
> >    +cc = ["akpm@linux-foundation.org"]
> > 
> > My understanding of Sashiko is quite limited, though.  Please correct me if I'm
> > wrong, Sashiko team.
> 
> Thanks, SJ.
> 
> I answered Andrew privately, but you’re right, the second option you suggested will subscribe Andrew to all mm reviews.

Thank you for confirming, Roman.

> Sorry, I did not understand, what limitation are you talking about here?
> The only limitation here is the variety of preferences by various maintainers: some push for reply_all lkml-wide,
> some hate sashiko’s emails in general.

What I wanted to say is that I'm not fully understanding Sashiko code, and
hence my above 'mailing_list.toml' edit suggestion might be wrong.  It was just
for giving Andrew a warning about my suggestion.  Now you confirmed my
suggestion is not wrong, so no problem here. :)


Thanks,
SJ

[...]

      reply	other threads:[~2026-10-12 22:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 22:06 email handling Andrew Morton
2026-10-12 21:25 ` SJ Park
2026-10-12 21:58   ` Roman Gushchin
2026-10-12 22:11     ` SJ Park [this message]

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=20261012221129.375576-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=roman.gushchin@linux.dev \
    --cc=sashiko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox