From: Sasha Levin <sashal@kernel.org>
To: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
Cc: Antheas Kapenekakis <lkml@antheas.dev>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [RFC v1 2/2] platform/x86/amd: Add AMD DPTCi driver
Date: Tue, 3 Mar 2026 16:44:54 -0500 [thread overview]
Message-ID: <aadWVjqVHjyEx7TX@laps> (raw)
In-Reply-To: <ab11076f-daf0-4e10-8ae6-e91dfc612a96@kernel.org>
On Tue, Mar 03, 2026 at 02:54:59PM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
>+ Sasha
>
>On 3/3/2026 2:40 PM, Antheas Kapenekakis wrote:
>>On Tue, 3 Mar 2026 at 21:10, Mario Limonciello (AMD) (kernel.org)
>><superm1@kernel.org> wrote:
>>>
>>>I'll preface this by saying - I don't have a problem with using an AI to
>>>help write a driver, but please disclose that it was done and that in
>>>this case even you haven't closely audited the results.
>>>
>>>I personally would never submit something generated by an LLM that I
>>>didn't audit and add a S-o-b tag to it (asserting I am willing to stand
>>>by the code).
>>>
>>>I'm glad that I found out it was AI written before I started to review
>>>the code, I would have had a lot more candid comments for you.
>>>
>>>There is a lot of weird stuff in this driver that I'm not going to
>>>comment on and nitpick, but I'll leave a few broad strokes things.
>>
>>Of course, to that end, feel free to skip a full review until I get to
>>properly rewriting it.
>>
>>What is the current stance on Co-bys for that? I'm trying to follow
>>the discussion but I missed the news. I can lint it properly next
>>time.
>>
>> From my perspective, pouring a month into a driver like this without
>>having a firm commitment that it will go somewhere is a bit hard to
>>stomach.
>
>Sure.
>
>I don't need a dedicated tag telling me what tool you wrote it with.
>I don't care if it was Opus, Gemini or Qwen3.5. They all can make
>mistakes that need to be audited.
>
>The most important part to me (or any reviewer) is a signal that I
>shouldn't invest more effort reviewing this than you did writing it
>and reviewing it.
>
>My feeling on this kind of RFC this is the most appropriate tag:
>
>Not-signed-off-by: Foo Bar <foo@bar.com>
We have docs for this now :) Both in the README file as well as
Documentation/process/coding-assistants.rst .
In particular, you should be upfront about using AI to generate code, using the
Assisted-by: tag, and definitely giving it a very careful review making sure
you completely understand what the code does.
As the README says:
The human submitter is responsible for:
* Reviewing all AI-generated code
* Ensuring compliance with licensing requirements
* Adding their own Signed-off-by tag to certify the DCO
* Taking full responsibility for the contribution
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-03 21:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 18:17 [RFC v1 0/2] platform/x86/amd: Add AMD DPTCi driver for TDP control in devices without vendor-specific controls Antheas Kapenekakis
2026-03-03 18:17 ` [RFC v1 1/2] Documentation: firmware-attributes: generalize save_settings entry Antheas Kapenekakis
2026-03-03 18:17 ` [RFC v1 2/2] platform/x86/amd: Add AMD DPTCi driver Antheas Kapenekakis
2026-03-03 20:10 ` Mario Limonciello (AMD) (kernel.org)
2026-03-03 20:40 ` Antheas Kapenekakis
2026-03-03 20:54 ` Mario Limonciello (AMD) (kernel.org)
2026-03-03 21:20 ` Antheas Kapenekakis
2026-03-03 21:44 ` Sasha Levin [this message]
2026-03-03 22:08 ` Antheas Kapenekakis
2026-03-03 18:59 ` [RFC v1 0/2] platform/x86/amd: Add AMD DPTCi driver for TDP control in devices without vendor-specific controls Mario Limonciello
2026-03-03 19:16 ` Antheas Kapenekakis
2026-03-03 19:23 ` Antheas Kapenekakis
2026-03-03 19:27 ` Armin Wolf
2026-03-03 19:34 ` Antheas Kapenekakis
2026-03-03 21:50 ` Armin Wolf
2026-03-03 23:47 ` Antheas Kapenekakis
2026-03-03 19:51 ` Mario Limonciello (AMD) (kernel.org)
2026-03-03 20:04 ` Antheas Kapenekakis
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=aadWVjqVHjyEx7TX@laps \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@kernel.org \
/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
Powered by JetHome