From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Kees Cook <kees@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
corbet@lwn.net, workflows@vger.kernel.org, josh@joshtriplett.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] docs: submitting-patches: (AI?) Tool disclosure tag
Date: Fri, 25 Jul 2025 00:55:28 +0000 [thread overview]
Message-ID: <aILWAELwozskfIgj@gallifrey> (raw)
In-Reply-To: <202507241651.5E9C803C70@keescook>
* Kees Cook (kees@kernel.org) wrote:
> On Thu, Jul 24, 2025 at 07:45:56PM -0400, Steven Rostedt wrote:
> > My thought is to treat AI as another developer. If a developer helps you
> > like the AI is helping you, would you give that developer credit for that
> > work? If so, then you should also give credit to the tooling that's helping
> > you.
> >
> > I suggested adding a new tag to note any tool that has done non-trivial
> > work to produce the patch where you give it credit if it has helped you as
> > much as another developer that you would give credit to.
>
> We've got tags to choose from already in that case:
>
> Suggested-by: LLM
For me, 'Suggested-by:' seems fine for where an LLM has
responded to a 'suggest improvements to this function'.
> or
>
> Co-developed-by: LLM <not@human.with.legal.standing>
> Signed-off-by: LLM <not@human.with.legal.standing>
>
> The latter seems ... not good, as it implies DCO SoB from a thing that
> can't and hasn't acknowledged the DCO.
Yeh, the Co-developed-by: isn't terrible, but in both that and the
Suggested-by: is there a standard for how you would refer to the tool?
IMHO it should not have an email address there otherwise it'll confuse tools
into cc'ing them.
Dave
>
> --
> Kees Cook
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2025-07-25 0:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 17:54 linux
2025-07-24 19:07 ` Konstantin Ryabitsev
2025-07-24 20:45 ` Kees Cook
2025-07-24 21:06 ` Laurent Pinchart
2025-07-24 21:12 ` Dr. David Alan Gilbert
2025-07-24 21:20 ` Kees Cook
2025-07-24 23:45 ` Steven Rostedt
2025-07-24 23:54 ` Kees Cook
2025-07-25 0:55 ` Dr. David Alan Gilbert [this message]
2025-07-25 1:06 ` Sasha Levin
2025-07-25 1:20 ` Dr. David Alan Gilbert
2025-07-25 1:52 ` Sasha Levin
2025-07-25 2:02 ` Steven Rostedt
2025-07-25 2:39 ` Sasha Levin
2025-07-25 11:29 ` Dr. David Alan Gilbert
2025-07-25 11:37 ` Laurent Pinchart
2025-07-25 11:49 ` Dr. David Alan Gilbert
2025-07-25 17:45 ` Al Viro
2025-07-25 22:40 ` Sasha Levin
2025-07-25 23:29 ` Dr. David Alan Gilbert
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=aILWAELwozskfIgj@gallifrey \
--to=linux@treblig.org \
--cc=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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