mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@hozed.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	Daniel Pereira <danielmaraboo@gmail.com>,
	Chen-Yu Yeh <chenyou910331@gmail.com>, Weijie Yuan <wy@wyuan.org>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Lorenzo Stoakes <ljs@kernel.org>, Kees Cook <kees@kernel.org>,
	Jori Koolstra <jkoolstra@xs4all.nl>,
	Jeff Layton <jlayton@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Mark Brown <broonie@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Brian Foster <bfoster@redhat.com>,
	Carlos Maiolino <cem@kernel.org>,
	David Disseldorp <ddiss@suse.de>,
	Jani Nikula <jani.nikula@intel.com>,
	Justin Stitt <justinstitt@google.com>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: remove Assisted-by references
Date: Sun, 18 Oct 2026 16:52:50 +0000	[thread overview]
Message-ID: <atT5YvJs3JYIkF5h@false> (raw)
In-Reply-To: <as-2MbhDdCN2trMe@laps>

On Wed, Oct 14, 2026 at 01:04:49PM -0400, Sasha Levin wrote:
> On Wed, Oct 14, 2026 at 10:54:54AM -0600, Jonathan Corbet wrote:
> > Sasha Levin <sashal@kernel.org> writes:
> > 
> > > Remove the Assisted-by sections from coding-assistants.rst,
> > > submitting-patches.rst, and the Italian, Brazilian Portuguese and Traditional
> > > Chinese translations, and drop the handling of the tag from checkpatch.
> > > 
> > > [1] https://lore.kernel.org/workflows/2026070224-unholy-commode-cf45@gregkh/
> > > [2] https://lwn.net/Articles/1099594/
> > > [3] https://lore.kernel.org/all/2026101327-cupid-legal-6cf6@gregkh/
> > > 
> > > Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> > > Reviewed-by: Kees Cook <kees@kernel.org>
> > > Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Signed-off-by: Sasha Levin <sashal@kernel.org>
> > > ---
> > > Changes in v2:
> > > - Expand the changelog with the background and the Maintainers Summit
> > >   discussion (Laurent, Krzysztof, Greg, Lorenzo).
> > > - Rebase on docs-next and also remove the Assisted-by sections from the
> > >   pt_BR and zh_TW translations there.
> > > - Collect tags.
> > > 
> > > v1: https://lore.kernel.org/all/20261009083137.3-1-sashal@kernel.org/
> > 
> > OK, I have applied this, thanks.
> 
> Thanks Jon!
> 
> Also ping re: the AGENTS.md patch. Without it, we'll get very mixed results
> with just this change, where agents will pick and choose different policies
> around Assisted-by: because nothing is pointing them to the actual guidelines
> we have.

I agree with the general maintainers summit consensus that the previous
policy was not functional for the original intent. A tag that generally
only has one field of "LLM" is redundant and useless.

That being said, I think it is a major mistake to entirely remove the tag.

What I would like to see is some clear strong guidance and culture that
if we are going to encourage new people, new language models, and new
types of tools that haven't been invented yet, we can and should include
some reference to what those tools are.

For instance, in this message my tag would be Assisted-by: Vim, Debian, Mutt

As an open minded skeptic of AI tools, I'd really like to see in
metadata that's easily searchable with grep on what tools others are
using. For instance, I'd really like to know the toolset that was used
to generate "Improve page refcount scalability" [1], but it was not 
immediately obvious where to find this information without Gemini's 
assistance.

My proposal would be that we re-instate "Assisted-by:" as an optional
but highly recommended tag to document any *legally significant* AI,
LLM, or really *any* tool which is not generally available under the
Debian Free software guidelines [2]

If someone would like to suggest a command-line focused AI toolchain and
a set of Agent skills or other prompts, I'd be happy to put together a
patchset. I'd really prefer to use a fully open source LLM with open 
training data, but I think that's asking for too much at this point.

[1] https://lore.kernel.org/lkml/CAHk-=wjLjgfwgSZ1RDk4YdNFcV0ntosMO5AmBoHD76Zb3HFY7Q@mail.gmail.com/
[2] https://wiki.debian.org/DebianFreeSoftwareGuidelines

      reply	other threads:[~2026-10-18 16:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 12:15 Sasha Levin
2026-10-13 12:19 ` Jeff Layton
2026-10-13 12:42 ` Jori Koolstra
2026-10-13 13:00 ` Krzysztof Kozlowski
2026-10-13 13:08 ` Vlastimil Babka (SUSE)
2026-10-13 13:10   ` Krzysztof Kozlowski
2026-10-13 13:15     ` Vlastimil Babka (SUSE)
2026-10-13 14:41 ` SJ Park
2026-10-13 14:47 ` David Hildenbrand (Arm)
2026-10-13 23:21   ` Shuah Khan
2026-10-13 15:04 ` Mark Brown
2026-10-13 17:43   ` Daniel Pereira
2026-10-14  3:11 ` Weijie Yuan
2026-10-14 16:36 ` Miguel Ojeda
2026-10-14 16:54 ` Jonathan Corbet
2026-10-14 17:04   ` Sasha Levin
2026-10-18 16:52     ` Troy Benjegerdes [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=atT5YvJs3JYIkF5h@false \
    --to=hozer@hozed.org \
    --cc=apw@canonical.com \
    --cc=axboe@kernel.dk \
    --cc=bfoster@redhat.com \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=cem@kernel.org \
    --cc=chenyou910331@gmail.com \
    --cc=corbet@lwn.net \
    --cc=danielmaraboo@gmail.com \
    --cc=david@kernel.org \
    --cc=ddiss@suse.de \
    --cc=dzm91@hust.edu.cn \
    --cc=federico.vaga@vaga.pv.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=jani.nikula@intel.com \
    --cc=jkoolstra@xs4all.nl \
    --cc=jlayton@kernel.org \
    --cc=joe@perches.com \
    --cc=justinstitt@google.com \
    --cc=kees@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@kernel.org \
    --cc=workflows@vger.kernel.org \
    --cc=wy@wyuan.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®