From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Chris Mason <mason@kernel.org>,
sashiko@lists.linux.dev,
Roman Gushchin <roman.gushchin@linux.dev>,
ast@kernel.org, kuba@kernel.org
Subject: Re: [RFC] reworking the review-prompts subsystem guide
Date: Tue, 6 Oct 2026 14:22:57 -0700 [thread overview]
Message-ID: <f8295279-7af7-4b3e-bc9b-112bfc49816b@linux.dev> (raw)
In-Reply-To: <91e21331-ed6d-4ac0-b237-b01aeadca2d1@app.fastmail.com>
On 10/2/26 12:04 PM, Chris Mason wrote:
> Hi everyone,
>
> I've been updating the review prompts, and you can find my current work here in the subsystem-build branch:
>
> https://github.com/masoncl/review-prompts.git subsystem-build
Hi Chris,
I've set up "shadow" AI reviews for BPF, taking advantage of our
existing bpf-rc infra. It's a copy of the entire BPF CI pipeline that
we occasionally use for testing of the CI itself.
The shadow reviews are using your new prompts from the subsystem-build
branch. The reviews are posted on kernel-patches/bpf-rc PRs as
comments and are not mailed to the list. I configured the reviews to
run on every 4th series (so 25% of prod). I'll let it run for some
time (couple of weeks?) and then we'll be able to analyze the
difference and either switch or iterate.
One quirk I added: a datetime cutoff of the semcode's lore archive, so
that the rc reviewer doesn't see prod reviewer's comments. Not sure
how reliable that'll be, because AI may potentially figure out to read
them from github or something. But we should notice if it doesn't
work.
You can find the relevant PRs like this:
$ gh pr list -R kernel-patches/bpf-rc --label ai-review-shadow:subsystem-build --state all --limit 50 \
--json url,headRefName,title --jq '.[] | "\(.url)\t\(.headRefName)\t\(.title)"'
Note the "ai-review-shadow:subsystem-build" PR label.
The reviews run with debug output, and also the claude session logs
are captured as artifacts. Ask your agent to write a script to pull
those in with github cli, should be easy.
I just pushed, it'll take a few days before we get any real samples.
Thank you for working on the prompts!
>
> [...]
next prev parent reply other threads:[~2026-10-06 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 19:04 [RFC] reworking the review-prompts subsystem guide Chris Mason
2026-10-02 21:18 ` Chuck Lever
2026-10-04 9:17 ` Chris Mason
2026-10-05 19:58 ` Jakub Kicinski
2026-10-05 21:14 ` Roman Gushchin
2026-10-05 21:53 ` Jakub Kicinski
2026-10-05 23:37 ` Ihor Solodrai
2026-10-06 21:22 ` Ihor Solodrai [this message]
2026-10-07 9:00 ` Chris Mason
2026-10-09 14:17 ` Fuad Tabba
2026-10-09 17:57 ` Chris Mason
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=f8295279-7af7-4b3e-bc9b-112bfc49816b@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=ast@kernel.org \
--cc=kuba@kernel.org \
--cc=mason@kernel.org \
--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.