On Thu, 12 Feb 2026 at 06:02, Chris Mason <[email protected]> wrote: > > > > On 2/11/26 2:44 PM, Dave Airlie wrote: > > Hi all, > > > > This came up at kernel maintainers summit, so I've been trying to see > > what I can piece together, and have a small demonstration that may be > > useful to some people. > > > > I didn't want to pollute the mailing list with AI patch reviews, so I > > decided to set up a public-inbox that the reviews are pushed into. > > This isn't currently automated, I'm just asking claude to pull the > > last 2-3 days of patches and review what is new every so often. > > > > The workflow use lei to pull mails to local PC, use review-prompts + > > my own prompt to try and review a patch series, both as a complete > > work, and per-patch reviews, then create the reply emails and put them > > into a public inbox git tree for publishing. > > > > I've no idea if it's using review-prompts properly or at all, this is > > all very vibe coded so far. > > > > https://urldefense.com/v3/__https://lore.gitlab.freedesktop.org/drm-ai-reviews/__;!!Bt8RZUm9aw!7ZGHjZ_cowu_q5cPVL_mOXmzkCeCUgALho-xJLBTCSi_FtnWbpG5rNYrxBZfhrfg24G7LkJ4$ > > > > This is a public inbox, you can also git clone > > > > https://urldefense.com/v3/__https://gitlab.freedesktop.org/drm/ai-reviews-public-inbox__;!!Bt8RZUm9aw!7ZGHjZ_cowu_q5cPVL_mOXmzkCeCUgALho-xJLBTCSi_FtnWbpG5rNYrxBZfhrfg27r4vy3o$ > > > > I'm currently just using my Red Hat provided claude with opus 4.6, > > until I get told I've burned enough money. > > > > The list below are the patches with reviews, if someone wants to look > > and give feedback on whether the reviews for their series are useful, > > find any bugs or regressions, that would be cool. > > > > I've bcc'd anyone who has a patch on the list. > > > > This is also just an experiment to see what might stick, it might > > disappear at any time, and it probably needs a lot of tuning. > > The output is pretty different from netdev/bpf: > > https://lore.kernel.org/bpf/?q=AI+reviewed+your+patch > > Which might be what you want so it's fine of course. But it looks like > it didn't actually go through the report generation from the review > prompts, so I'm worried it didn't use the rest of the prompts either. > > My stuff should be creating a review-inline.txt which is the lkml > formatted review. > > I'm happy to try things out here if it'll help.
My plan over the next few days is to refine the code to make sure it's doing this, my prompt asks it to load the patch and the kernel prompts, then do a review across the series and individual patches, I'm guessing some of the results aren't making it back out the other side. Dave.
