All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	 Linus Torvalds <torvalds@linux-foundation.org>,
	Justin Stitt <justinstitt@google.com>,
	 Carlos Maiolino <cem@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	 Jori Koolstra <jkoolstra@xs4all.nl>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	 Brian Foster <bfoster@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	 David Disseldorp <ddiss@suse.de>,
	Mark Brown <broonie@kernel.org>,
	 Jani Nikula <jani.nikula@intel.com>,
	Jens Axboe <axboe@kernel.dk>,
	 David Hildenbrand <david@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	 Christian Brauner <brauner@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	workflows@vger.kernel.org,  linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] docs: link AI coding assistants and tool-generated content pages
Date: Fri, 3 Jul 2026 09:18:46 +0100	[thread overview]
Message-ID: <akdv9GCjOrs_6DM6@lucifer> (raw)
In-Reply-To: <20260702182632.GK3534761@killaraus.ideasonboard.com>

On Thu, Jul 02, 2026 at 09:26:32PM +0300, Laurent Pinchart wrote:
> On Thu, Jul 02, 2026 at 05:49:01PM +0100, Lorenzo Stoakes wrote:
> > Both of these guidelines are complimentary to one another - one specifying
> > guidelines on AI coding assistants, and the other specifying those for
> > tool-generated content.
> >
> > Since they are complimentary to one another, provide a link to each in the
> > other.
> >
> > Signed-off-by: Lorenzo Stoakes <ljs@kernel.org>
> > ---
> >  Documentation/process/coding-assistants.rst | 4 ++++
> >  Documentation/process/generated-content.rst | 7 +++++++
> >  2 files changed, 11 insertions(+)
> >
> > diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst
> > index 899f4459c52d..6125ee4914c5 100644
> > --- a/Documentation/process/coding-assistants.rst
> > +++ b/Documentation/process/coding-assistants.rst
> > @@ -15,6 +15,10 @@ kernel development process:
> >  * Documentation/process/coding-style.rst
> >  * Documentation/process/submitting-patches.rst
> >
> > +For guidelines on content generated by AI coding assistants see:
> > +
> > +* Documentation/process/generated-content.rst
> > +
>
> It could be worth it checking if this increases the likelyhood that an
> agent would include a disclosure statement in patches. I would have
> assumed that the "Attribution" section in this file to be enough. Has
> anyone ever tried to understand why it doesn't work and if it can be
> improved ?

I don't think so AFAIK.

I think people generally are aware of the Assisted-by as a thing, but perhaps
less so of the generated content guidelines, so hopefully this helps that a
little!

>
> Maybe a stronger statement would help here:
>
> "Furthermore, AI tools must follow the guidelines for generated content
> documented in Documentation/process/generated-content.rst."

I mean I would like that actually, _but_, I wanted to keep this as neutral as
possible for the time being so we can first establish the links without
controversy ;)

Then we can perhaps separately think about making the language a little more
insistent :)

>
> >  Licensing and Legal Requirements
> >  ================================
> >
> > diff --git a/Documentation/process/generated-content.rst b/Documentation/process/generated-content.rst
> > index 08621e50a462..aad2caad9f8b 100644
> > --- a/Documentation/process/generated-content.rst
> > +++ b/Documentation/process/generated-content.rst
> > @@ -107,3 +107,10 @@ the resulting changes.
> >
> >  If you do so anyway, maintainers are entitled to reject your series
> >  without detailed review.
> > +
> > +References
> > +==========
> > +
> > +For specific guidelines on AI coding assistants, see:
> > +
> > +* Documentation/process/coding-assistants.rst
>
> --
> Regards,
>
> Laurent Pinchart

Cheers, Lorenzo

  reply	other threads:[~2026-07-03  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 16:49 [PATCH] docs: link AI coding assistants and tool-generated content pages Lorenzo Stoakes
2026-07-02 16:55 ` Jeff Layton
2026-07-02 17:12 ` David Hildenbrand (Arm)
2026-07-02 18:26 ` Laurent Pinchart
2026-07-03  8:18   ` Lorenzo Stoakes [this message]
2026-07-02 22:00 ` SJ Park
2026-07-03  6:05 ` Greg KH
2026-07-03  8:09 ` Vlastimil Babka (SUSE)

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=akdv9GCjOrs_6DM6@lucifer \
    --to=ljs@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bfoster@redhat.com \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=cem@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=ddiss@suse.de \
    --cc=hch@infradead.org \
    --cc=jani.nikula@intel.com \
    --cc=jkoolstra@xs4all.nl \
    --cc=jlayton@kernel.org \
    --cc=justinstitt@google.com \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.