All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: SJ Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Justin Stitt <justinstitt@google.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.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: Thu,  2 Jul 2026 15:00:37 -0700	[thread overview]
Message-ID: <20260702220037.97787-1-sj@kernel.org> (raw)
In-Reply-To: <20260702164901.121128-1-ljs@kernel.org>

On Thu,  2 Jul 2026 17:49:01 +0100 Lorenzo Stoakes <ljs@kernel.org> 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.

Makes perfect sense to me.

> 
> Signed-off-by: Lorenzo Stoakes <ljs@kernel.org>

Acked-by: SJ Park <sj@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:

A comma after 'assistants' is missed?

> +
> +* Documentation/process/generated-content.rst
> +
>  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:

Or, a comma is unnecessarily added after 'assistants'.

Whatever, I think keeping those identical is better.


Thanks,
SJ

[...]

  parent reply	other threads:[~2026-07-02 22:00 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
2026-07-02 22:00 ` SJ Park [this message]
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=20260702220037.97787-1-sj@kernel.org \
    --to=sj@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=ljs@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.