From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>,
Yosry Ahmed <yosry@kernel.org>
Cc: "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>,
SeongJae Park <sj@kernel.org>
Subject: Re: Sashiko change proposal
Date: Fri, 16 Oct 2026 09:56:32 +0200 [thread overview]
Message-ID: <97dcba80-40bb-4b2c-a8bb-8a98b82e7d2a@kernel.org> (raw)
In-Reply-To: <7ia4bj8ufqlw.fsf@castle.c.googlers.com>
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:
>>>
>>> (CCing all people attending the mm-next call)
>>>
>>> Hi,
>>>
>>> After talking to Roman at MS, he just informed me that sashiko now has a new
>>> feature combination:
>>> - "embargo_hours": hours before review is public + emails sent
>>> - Mechanism for signed-in maintainers to lift embargo immediately
>>>
>>> That solves the key issue I had with sashiko: people/agents re-spinning stuff
>>> too fast before a human at least had the chance to jump in first.
>>>
>>> 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)
>>>
>>> I'd say we start with 24h and see how it goes.
>>>
>>> Thoughts?
>>
>> Thanks for doing this, it's much more convenient to notice and respond
>> to the review when Sashiko replies to the patches.
>>
>> FWIW, I prefer no 24hr embargo, seems to work well on the KVM side --
>> but I will take what I can get :P
>>
>> Reviewed-by: Yosry Ahmed <yosry@kernel.org>
>
> Is it time for me to pick up the change? David, I'll let you decide when
> the discussion is done or just send me a PR, up to you.
I was under the assumption that I would have to open a PR on github, but if you
could just perform the change yourself, that would be great.
I don't think there is any pushback right now, and we can always adjust if we
realize this doesn't work the way we wanted to.
--
Cheers,
David
prev parent reply other threads:[~2026-10-16 7:56 UTC|newest]
Thread overview: 14+ 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 22:38 ` Yosry Ahmed
2026-10-16 0:15 ` Roman Gushchin
2026-10-16 7:56 ` David Hildenbrand (Arm) [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=97dcba80-40bb-4b2c-a8bb-8a98b82e7d2a@kernel.org \
--to=david@kernel.org \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=chriscli@google.com \
--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=sj@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox