From: Chih-En Lin <shiyn.lin@gmail.com>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: sashiko@lists.linux.dev, Chris Mason <mason@kernel.org>,
rawat10@purdue.edu, pfonseca@purdue.edu
Subject: Re: [RFC] new design of review prompts management
Date: Thu, 22 Oct 2026 21:16:16 -0400 [thread overview]
Message-ID: <20261023011616.GA6628@laptop01> (raw)
In-Reply-To: <7ia45wyty0ph.fsf@castle.c.googlers.com>
On Thu, Oct 22, 2026 at 07:50:02PM +0000, Roman Gushchin wrote:
> Chih-En Lin <shiyn.lin@gmail.com> writes:
>
> > Hi all,
>
> Hello,
>
> Thank you for the proposal!
Hi,
Thanks for the reply!
> Many ideas here resonate with what I was working on/was thinking of
> recently. I'm about to publish a big rework of prompts which separates
> them in auto-generated part and subjective small part for maintainers.
I wonder if that are:
https://lore.kernel.org/sashiko/91e21331-ed6d-4ac0-b237-b01aeadca2d1@app.fastmail.com/
https://github.com/masoncl/review-prompts.git subsystem-build
> It's somewhat close to what you're proposing, but not fully. Let's maybe
> restart this discussion after this?
Sure :-)
> I'm sure there will be a ton of room for further improvements...
We actually have other more ideas (included and not included in [1]) to
improve this type of patch review system, but most of them are based on
the invariant unit. And, since the kernel community has one already, we
are happy to contribute.
Thanks,
Chih-En Lin
---
[1] https://arxiv.org/abs/2603.24825
next prev parent reply other threads:[~2026-10-23 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 23:44 [RFC] new design of review prompts management Chih-En Lin
2026-10-22 19:50 ` Roman Gushchin
2026-10-23 1:16 ` Chih-En Lin [this message]
2026-10-23 1:26 ` 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=20261023011616.GA6628@laptop01 \
--to=shiyn.lin@gmail.com \
--cc=mason@kernel.org \
--cc=pfonseca@purdue.edu \
--cc=rawat10@purdue.edu \
--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 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.