From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
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, sj@kernel.org, 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: Thu, 15 Oct 2026 13:27:47 +0200 [thread overview]
Message-ID: <60fb38c4-b9f3-4146-ab5c-ed16c95a2c7e@kernel.org> (raw)
In-Reply-To: <2vxz4ieni4w2.fsf@kernel.org>
On 10/15/26 13:23, Pratyush Yadav wrote:
> On Thu, Oct 15 2026, David Hildenbrand (Arm) 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.
>
> If a sender re-spins stuff too fast after a Sashiko review, that's a
> pretty clear signal that it is an agent.
And I know for sure that that's not always the case.
--
Cheers,
David
next prev parent reply other threads:[~2026-10-15 11:27 UTC|newest]
Thread overview: 8+ 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) [this message]
2026-10-15 12:07 ` Harry Yoo
2026-10-15 12:15 ` 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=60fb38c4-b9f3-4146-ab5c-ed16c95a2c7e@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=pratyush@kernel.org \
--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=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