From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Michal Simek <michal.simek@amd.com>
Subject: Re: AI-assisted review
Date: Tue, 26 May 2026 08:04:54 +0200 [thread overview]
Message-ID: <a4d2844a-db8d-4fef-b0e4-443e6e4fb550@kernel.org> (raw)
In-Reply-To: <20260525143951.GK1858239@bill-the-cat>
On 25/05/2026 16:39, Tom Rini wrote:
> On Mon, May 25, 2026 at 03:29:50PM +0100, Josh Law wrote:
>> On May 25, 2026 3:27:18 PM GMT+01:00, Tom Rini <trini@konsulko.com> wrote:
>>> On Mon, May 25, 2026 at 03:25:19PM +0100, Josh Law wrote:
>>>>
>>>> But most projects do generally ban AI anything.
>>>>
>>>> Idk what we could do for u-boot when it comes to a sashiko like
>>> solution.
>>>>
>>>> Maybe we could talk about it?
>>>
>>> Proposing a policy for the project about AI (and indeed not just linking
>>> to other projects which have what I find to be helpful references) is on
>>> the TODO list for the project leadership committee. We've just been
>>> busily handling other issues for a while now, unfortunately.
For kernel:
https://web.git.kernel.org/pub/scm/linux/kernel/git/docs/linux.git/commit/?h=docs-next&id=48c3876a6a6f78578ccd0fec71ef67fd6a3fd6f5
>>>
>>>
>>
>> I could put something into suggestion:
>>
>>
>> So, for patches: you could do assisted bys, and it depends on the
>> maintainer, etc etc like Linux,
>>
>>
>> And for reviews: that's actually hard to think about, because some
>> maintainers love using AI review tools because it's useful, others
>> don't particularly like tools like that, maybe a opt-in "reviewman"?
>>
>> But tbh that's up for discussion.
>
> Thanks for offering, but it's going to be a large / contentious enough
> issue that we haven't gotten to it yet, unfortunately.
>
Before you waste too much time, that person uses vibe coding without any
control and without any supervision, so that's basically AI slop.
Also, in terms of reviewing whatever review they would provide has
little value. I am sure Josh Law would be happy to give "AI-slop" review
and get tags for that.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-26 6:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 21:03 AI-assisted review Simon Glass
2026-05-15 22:07 ` Tom Rini
2026-05-18 8:55 ` Michal Simek
2026-05-18 15:58 ` Tom Rini
2026-05-25 14:03 ` Simon Glass
2026-05-25 14:11 ` Josh Law
2026-05-25 14:21 ` Tom Rini
2026-05-25 14:25 ` Josh Law
2026-05-25 14:27 ` Tom Rini
2026-05-25 14:29 ` Josh Law
2026-05-25 14:39 ` Tom Rini
2026-05-25 14:41 ` Josh Law
2026-05-26 6:04 ` Krzysztof Kozlowski [this message]
2026-05-26 14:18 ` Tom Rini
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=a4d2844a-db8d-4fef-b0e4-443e6e4fb550@kernel.org \
--to=krzk@kernel.org \
--cc=michal.simek@amd.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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