From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kees Cook <kees@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, skhan@linuxfoundation.org,
rdunlap@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: add AGENTS.md as a symlink to README
Date: Fri, 25 Sep 2026 10:18:56 +0300 [thread overview]
Message-ID: <20260925071856.GH135998@killaraus.ideasonboard.com> (raw)
In-Reply-To: <202609241709.8B710211@keescook>
On Thu, Sep 24, 2026 at 05:12:15PM -0700, Kees Cook wrote:
> On Thu, Sep 24, 2026 at 09:49:45AM -0400, Sasha Levin wrote:
> > Add a top-level AGENTS.md symlink to README, so agents load it on their
> > own and follow its pointer to the AI guidelines. This keeps a single
> > entry point for every reader, and avoids adding a separate copy of the
> > policy that could drift from the RST.
>
> Yeah, I think this is fine. I don't want a separate file just for
> Agents: we intentionally designed the README to work for them. That
> there are Agents missing it is sad, but okay. And the Agents are already
> trained to deal with for-human docs, so that it adds more tokens
> shouldn't matter here since it's tiny. (If it reads the contribution
> docs before every patch creation that seems like a good thing?)
>
> Acked-by: Kees Cook <kees@kernel.org>
It won't come as a surprise, but I want to voice opposition to
encouraging users to use AI agents for kernel development. This patch
does so, so NAK.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-09-25 7:19 UTC|newest]
Thread overview: 9+ 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 [this message]
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=20260925071856.GH135998@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.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®