The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
	 Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Boris Burkov <boris@bur.io>, Jeff Layton <jlayton@kernel.org>,
	 Greg KH <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 Jonathan Corbet <corbet@lwn.net>,
	Justin Stitt <justinstitt@google.com>,
	 Carlos Maiolino <cem@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	 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>,
	Vlastimil Babka <vbabka@kernel.org>,
	 "Christian Brauner (Amutable)" <brauner@kernel.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Documentation: remove the requirement for LLM attribution
Date: Tue, 7 Jul 2026 11:20:09 +0100	[thread overview]
Message-ID: <akzSY47Rjn7TDOL6@lucifer> (raw)
In-Reply-To: <1778033301.182575.1783419343917@kpc.webmail.kpnmail.nl>

On Tue, Jul 07, 2026 at 12:15:43PM +0200, Jori Koolstra wrote:
>
> I haven't really seen anyone opposed the following I wrote earlier:
>
> - it's more relevant to know how an LLM was used than that it was used (and the
>   tag is just a quick indication of this)
> - advertising for particular corporations does not really serve any purpose to
>   the community, so just say "LLM"
> - the tags may be used to prevent arguing
> - the requirement to be open about LLM use (whether by tags or whatever) makes
>   it easier for maintainers (if they feel the need) to de-prioritize patches
>   by someone unwilling to abide by these rules whenever the maintainer perceives
>   or suspects prior undeclared LLM use. This prevents an asymmetrical situation
>   of LLM slop being produced much faster that what can be reviewed.

Yup completely agree.

I just want to get something merged rather than just talk :) and so to avoid any
_possible_ argument 'keep it like it is but add a comment' is a much, much
easier sell to everybody.

Then we can follow up with anything else one we get _something useful merged_ :)

>
> Perhaps the last point is more controversial.

Not in my opinion. We're only at the beginning of this horror show and I think
far stronger measures will eventually be needed (e.g. newcomes will have to
build trust first, which sucks, but it may be the only practical solution).

>
> I would really like to adept the systemd policy text.[1] If I have time later today
> I'll try to write something up... although maybe it is too ambitious :)
>
> [1]: https://lore.kernel.org/linux-fsdevel/20260702-bahnen-ertappen-verspannungen-0eaaf1e3f5af@brauner/

:)

Cheers, Lorenzo

  reply	other threads:[~2026-07-07 10:20 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 14:32 [PATCH] Documentation: remove the requirement for LLM attribution Jeff Layton
2026-07-02 14:53 ` Laurent Pinchart
2026-07-02 14:58   ` Lorenzo Stoakes
2026-07-02 15:02   ` Jeff Layton
2026-07-02 15:07     ` Lorenzo Stoakes
2026-07-02 14:57 ` Lorenzo Stoakes
2026-07-02 15:28   ` Laurent Pinchart
2026-07-02 15:36     ` Lorenzo Stoakes
2026-07-02 15:44       ` Laurent Pinchart
2026-07-02 15:07 ` Greg KH
2026-07-02 15:13   ` Jonathan Corbet
2026-07-02 15:20     ` Lorenzo Stoakes
2026-07-02 18:46     ` Andreas Dilger
2026-07-03  2:57       ` Theodore Tso
2026-07-03 11:50         ` Jori Koolstra
2026-07-03 16:12         ` Andreas Dilger
2026-07-02 15:15   ` Lorenzo Stoakes
2026-07-02 15:33   ` Jori Koolstra
2026-07-02 15:37     ` Lorenzo Stoakes
2026-07-02 15:36   ` Laurent Pinchart
2026-07-02 15:57   ` Jeff Layton
2026-07-02 16:13     ` Laurent Pinchart
2026-07-02 16:19       ` Greg KH
2026-07-02 16:32         ` Laurent Pinchart
2026-07-03  6:37           ` Greg KH
2026-07-03  7:23             ` David Hildenbrand (Arm)
2026-07-03  7:30               ` Greg KH
2026-07-03  7:33                 ` David Hildenbrand (Arm)
2026-07-03 11:42                 ` Theodore Tso
2026-07-03 11:53                   ` Laurent Pinchart
2026-07-03 12:04                   ` Jori Koolstra
2026-07-06  8:44                   ` Mauro Carvalho Chehab
2026-07-02 16:48         ` Jeff Layton
2026-07-02 16:50           ` Lorenzo Stoakes
2026-07-02 21:17             ` Boris Burkov
2026-07-02 23:17               ` SJ Park
2026-07-03  7:05               ` David Hildenbrand (Arm)
2026-07-03 13:12                 ` Lorenzo Stoakes
2026-07-03 16:32                   ` Laurent Pinchart
2026-07-03 18:22                     ` David Hildenbrand (Arm)
2026-07-07  9:20                       ` Lorenzo Stoakes
2026-07-07  9:49                         ` David Hildenbrand (Arm)
2026-07-07  9:55                           ` Lorenzo Stoakes
2026-07-07 13:29                             ` David Hildenbrand (Arm)
2026-07-07 10:01                           ` Geert Uytterhoeven
2026-07-07 13:31                             ` David Hildenbrand (Arm)
2026-07-07 12:40                           ` Laurent Pinchart
2026-07-07 13:28                             ` David Hildenbrand (Arm)
2026-07-07 14:18                               ` Laurent Pinchart
2026-07-07 10:15                         ` Jori Koolstra
2026-07-07 10:20                           ` Lorenzo Stoakes [this message]
2026-07-03 18:26                   ` David Hildenbrand (Arm)
2026-07-02 23:05             ` SJ Park
2026-07-02 16:11 ` Chuck Lever
2026-07-02 16:14   ` Lorenzo Stoakes

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=akzSY47Rjn7TDOL6@lucifer \
    --to=ljs@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bfoster@redhat.com \
    --cc=boris@bur.io \
    --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=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox