From: SJ Park <sj@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: SJ Park <sj@kernel.org>, Harry Yoo <harry@kernel.org>,
David Hildenbrand <david@kernel.org>,
linux-mm@kvack.org, ackerleytng@google.com,
akpm@linux-foundation.org, chriscli@google.com,
hannes@cmpxchg.org, jack@suse.cz, liam@infradead.org,
muchun.song@linux.dev, shakeelb@meta.com, ziy@nvidia.com,
Lorenzo Stoakes <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 07:46:02 -0700 [thread overview]
Message-ID: <20261015144603.106449-1-sj@kernel.org> (raw)
In-Reply-To: <9139A421-50DE-45E1-99D5-4EFBD4225A98@linux.dev>
On Thu, 15 Oct 2026 05:15:05 -0700 Roman Gushchin <roman.gushchin@linux.dev> wrote:
> > On Oct 15, 2026, at 5:08 AM, Harry Yoo <harry@kernel.org> wrote:
[...]
> > Quick question: when are maintainers supposed to lift embargo?
>
> They don’t have to: it will be lifted automatically after 24h (or whatever is configured).
> But if you as a maintainer has an immediate comment to Sashiko’s review or you’re ready to pick the change, you can lift it immediately.
> And of course maintainers can see review results immediately.
The maintainer feature sounds cool. I was wondering how I could do this in
detail. This "What's New in Sashiko" [1] is kindly explaining it.
: Maintainer embargo access & early embargo release
: Signed-in maintainers can view embargoed reviews immediately without waiting
: for the timer, and use the new "Release Embargo" button on a patchset page to
: publish results early.
By the way the "What's New in Sashiko" is very helpful new feature. I will
visit Sashiko web ui more frequently. Thank you Roman and Sashiko team for the
great works!
[1] https://github.com/sashiko-dev/sashiko/blob/main/static/index.html#L1894
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-10-15 14:46 UTC|newest]
Thread overview: 11+ 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 [this message]
2026-10-15 14:47 ` Zi Yan
2026-10-15 14:51 ` 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=20261015144603.106449-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=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