All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: SJ Park <sj@kernel.org>,
	"David Hildenbrand (Arm)" <david@kernel.org>,
	Yosry Ahmed <yosry@kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	ackerleytng@google.com, akpm@linux-foundation.org,
	chriscli@google.com, hannes@cmpxchg.org, harry@kernel.org,
	jack@suse.cz, liam@infradead.org, muchun.song@linux.dev,
	shakeelb@meta.com, ziy@nvidia.com,
	"Lorenzo Stoakes (Arm)" <ljs@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: Sashiko change proposal
Date: Sun, 18 Oct 2026 15:48:28 -0700	[thread overview]
Message-ID: <20261018224830.160147-1-sj@kernel.org> (raw)
In-Reply-To: <7ia4o6ct7lqi.fsf@castle.c.googlers.com>

On Fri, 16 Oct 2026 14:39:49 +0000 Roman Gushchin <roman.gushchin@linux.dev> wrote:

> "David Hildenbrand (Arm)" <david@kernel.org> writes:
> 
> > On 10/16/26 02:15, Roman Gushchin wrote:
> >> Yosry Ahmed <yosry@kernel.org> writes:
> >> 
> >>> On Thu, Oct 15, 2026 at 1:38 AM David Hildenbrand (Arm)
> >>> <david@kernel.org> wrote:
[...]
> >>>> I suggest the following sashiko change for linux-mm:
> >>>>
> >>>> diff --git a/projects/linux/mailing_lists.toml b/projects/linux/mailing_lists.toml
> >>>> index a9198de..ba123da 100644
> >>>> --- a/projects/linux/mailing_lists.toml
> >>>> +++ b/projects/linux/mailing_lists.toml
> >>>> @@ -46,7 +46,6 @@ ignored_emails = ["patchwork@emeril.freedesktop.org"]
> >>>>  ["linux-integrity@vger.kernel.org"]
> >>>>  ["linux-kernel@vger.kernel.org"]
> >>>>  ["linux-kselftest@vger.kernel.org"]
> >>>> -["linux-mm@kvack.org"]
> >>>>  ["linux-nvme@lists.infradead.org"]
> >>>>  ["linux-omap@vger.kernel.org"]
> >>>>  ["linux-pm@vger.kernel.org"]
> >>>> @@ -315,3 +314,7 @@ reply_to = ["author", "list", "recipients"]
> >>>>
> >>>>  ["fsverity@lists.linux.dev"]
> >>>>  reply_to = ["author", "list", "recipients"]
> >>>> +
> >>>> +["linux-mm@kvack.org"]
> >>>> +reply_to = ["author", "list", "recipients"]
> >>>> +embargo_hours = 24
> >>>>
> >>>>
> >>>> Which means:
> >>>> - Embargo 24h
> >>>> - Mails sent to everybody (author, list, CC list)
> >>>> - No positive-review ("looks great") mails (default)
> >>>> - No other static email addresses that receive a copy (default)
> >>>> - No additional ignored author email addresses (default)
[...]
> https://github.com/sashiko-dev/sashiko/pull/699/ , landed.
> 
> I'll roll it out later today.

Now linux-mm@ and damon@ has slightly different configs.  damon@ has no
embabrgo but send mails to only the author and the mailing list.  It is a
faster but narrower-scoped delivery setup.

I was assuming linux-mm@ side change will not make any change to damon@ side,
but apparently it is not.  DAMON patches Cc linux-mm@, and seems it results in
applying linux-mm@ side setup.  For example, this patch [1] got a sashiko
review, but it was marked as embargo on sashiko.dev.  I found and clicked a
button for releasing it.  It resulted in sending the review mail to all
recipients, not just the author and damon@ mailing list.  Correct me if I'm
wrong.

Could we keep the old behavior for DAMON patches?  For example, let damon@
setup to override linux-mm@ setup for DAMON patches.  After a second thought, I
realize this would be not very simple.  Identifying if a given patch is for
DAMON or not is implicit.  Maybe we could see if the subject contains "damon"
keyword...?  Still not perfect but maybe work for most cases?

For now, I will release damon@ patch reviews as soon as I find.  I don't mind
clicking the button multiple times, but I'm slightly concerned if someone might
be distracted, because DAMON patch review mails will be delivered to not only
the author and damon@ list but all recipients.  Please let me know if that
really distracts you.  Let's find a way if that's the case.

[1] https://lore.kernel.org/20261018220253.158238-1-sj@kernel.org/


Thanks,
SJ

[...]


  reply	other threads:[~2026-10-18 22:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  8:38 Sashiko change proposal David Hildenbrand (Arm)
2026-10-15  8:46 ` Lorenzo Stoakes (ARM)
2026-10-15  9:28 ` Mike Rapoport
2026-10-15  9:35 ` Vlastimil Babka (SUSE)
2026-10-15 11:23 ` Pratyush Yadav
2026-10-15 11:27   ` David Hildenbrand (Arm)
2026-10-15 12:07 ` Harry Yoo
2026-10-15 12:15   ` Roman Gushchin
2026-10-15 14:46     ` SJ Park
2026-10-15 14:47 ` Zi Yan
2026-10-15 14:51 ` SJ Park
2026-10-15 20:58 ` Andrew Morton
2026-10-16  7:33   ` David Hildenbrand (Arm)
2026-10-15 22:38 ` Yosry Ahmed
2026-10-16  0:15   ` Roman Gushchin
2026-10-16  7:56     ` David Hildenbrand (Arm)
2026-10-16 14:39       ` Roman Gushchin
2026-10-18 22:48         ` SJ Park [this message]
2026-10-18 23:07           ` SJ Park

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=20261018224830.160147-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=ackerleytng@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=chriscli@google.com \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=harry@kernel.org \
    --cc=jack@suse.cz \
    --cc=liam@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=rppt@kernel.org \
    --cc=shakeelb@meta.com \
    --cc=vbabka@kernel.org \
    --cc=willy@infradead.org \
    --cc=yosry@kernel.org \
    --cc=ziy@nvidia.com \
    /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.