From: Sasha Levin <sashal@kernel.org>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, skhan@linuxfoundation.org,
rdunlap@infradead.org, linux-kernel@vger.kernel.org,
"kees@kernel.org" <kees@kernel.org>
Subject: Re: [PATCH] docs: add AGENTS.md as a symlink to README
Date: Tue, 29 Sep 2026 10:02:46 -0400 [thread overview]
Message-ID: <arvFBqreU0qahkXx@laps> (raw)
In-Reply-To: <CAGwozwGc62HAJnLeYL+jq_PnJq1LsV3Ex9LtQTE1pX3144MdtA@mail.gmail.com>
On Sun, Sep 27, 2026 at 05:24:46PM +0200, Antheas Kapenekakis wrote:
>On Sun, 27 Sept 2026 at 16:06, Sasha Levin <sashal@kernel.org> wrote:
>> If someone adds their sign-off without understanding what it certifies,
>> that's on them. We can't have agents add it for them just because some
>> people would ignore its meaning anyway.
>
>I didn't say we should make the agent add it. I said if someone wants
>to do it it is up to them. Not you, not the mainline kernel config,
>not this patch. And disabling it does nothing because the user does
>not understand what a sign off is anyway and will add it later or
>submit without it. In which case you get broken patches anyway and you
>solved nothing.
Again, that's on the user. Your argument is saying that we should just drop
this whole DCO nonsense because no one understands it anyway.
We can't stop enforcing things just because users don't bother reading the
docs.
Nothing is stopping you from changing this behavior to your liking either, but
at that point it makes you a downstream consumer on the kernel, so you get to
carry that delta.
>> If you think a hand-written AGENTS.md would do better, feel free to
>> write one and propose it. For now, this one seems to be working just
>> fine.
>
>No, I am fine with one not existing and it would be my preference
>actually. Ideally it would be added to .gitignore as well.
>
>That just does not address your need of steering novel contributor
>plus LLM, which I tried to help with. But if you do not want to put
>more effort than a symlink then not breaking our workflows is more
>important so this patch should not merge.
All I care about is having all these "agents" follow the rules and guidelines
that the kernel community set around LLM contributions. I'm not trying to
improve the quality or make it more efficient. This patch is purely about
having the majority of LLM agents follow our rules out of the box.
If you want to spend a few months trying to massage an AGENTS.md to the liking
of your LLMs-of-choice, then go at it.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-29 14:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:49 Sasha Levin
2026-09-24 14:31 ` Theodore Tso
2026-09-24 15:18 ` Sasha Levin
2026-09-24 15:08 ` Bradley Morgan
2026-09-24 15:20 ` Sasha Levin
2026-09-24 15:44 ` Bradley Morgan
2026-09-24 16:57 ` Sasha Levin
2026-09-25 0:12 ` Kees Cook
2026-09-25 7:18 ` Laurent Pinchart
2026-09-26 11:12 ` Antheas Kapenekakis
2026-09-26 15:48 ` Sasha Levin
2026-09-26 17:54 ` Antheas Kapenekakis
2026-09-27 1:13 ` Sasha Levin
2026-09-27 2:42 ` Antheas Kapenekakis
2026-09-27 14:06 ` Sasha Levin
2026-09-27 15:24 ` Antheas Kapenekakis
2026-09-29 14:02 ` Sasha Levin [this message]
2026-09-29 15:02 ` Antheas Kapenekakis
2026-09-29 16:10 ` Antheas Kapenekakis
2026-09-29 16:35 ` Joshua Peisach
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=arvFBqreU0qahkXx@laps \
--to=sashal@kernel.org \
--cc=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.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
all inboxes | Powered by JetHome®