From: ckadr1 <ckadr1@gmx.net>
To: brauner@kernel.org
Cc: axboe@kernel.dk, corbet@lwn.net, david@kernel.org,
jlayton@kernel.org, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, vbabka@kernel.org,
workflows@vger.kernel.org
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Tue, 7 Jul 2026 20:55:35 +0200 [thread overview]
Message-ID: <5a789547-5c7c-488f-ad5f-3642c6c36d6b@gmx.net> (raw)
In-Reply-To: <20f91215-f0db-4bb5-9ada-f3df33d78534@gmx.net>
Hi,
I agree that providing an advertizing platform for LLM/LAM/MCP/A2A
providers should be avoided.
Detailed information could still be provided in announcements or the
mailing list if others might be interested.
There will be public discussions about who used/likes/prefers whatever
model/tool for whatever task anyway.
With the patch itself, maybe it might be important to know how AI
has been used/helped to create it. Copy+paste code from AI / getting
code from AI but verify,rework,adjust manually / getting the basic idea
or how to overcome issues, but coding done by humans / comments
provided by AI ...
This dicussion might be the easiest part imagining the future.
What if the patch/feature would actually make use of MCP/A2A - that's a
different story. Local guardrails need to be guaranteed, remote ones
requested from the endpoint, eventually dropped if not satisfied like in
a failed TLS handshake.
Just my 2c,
Christian
next prev parent reply other threads:[~2026-07-07 18:55 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 15:54 Christian Brauner
2026-07-01 16:08 ` Mark Brown
2026-07-02 7:10 ` Christian Brauner
2026-07-02 11:35 ` Mark Brown
2026-07-01 16:08 ` Jonathan Corbet
2026-07-01 16:12 ` David Hildenbrand (Arm)
2026-07-02 7:11 ` Christian Brauner
2026-07-02 9:51 ` David Disseldorp
2026-07-01 16:10 ` David Hildenbrand (Arm)
2026-07-02 7:27 ` Christian Brauner
2026-07-02 7:46 ` David Hildenbrand (Arm)
2026-07-02 8:10 ` Laurent Pinchart
2026-07-02 8:16 ` David Hildenbrand (Arm)
2026-07-02 10:04 ` Lorenzo Stoakes
2026-07-02 11:51 ` David Hildenbrand (Arm)
2026-07-02 12:49 ` Lorenzo Stoakes
2026-07-02 13:41 ` Jani Nikula
2026-07-02 13:48 ` Jeff Layton
2026-07-02 13:26 ` Christian Brauner
2026-07-02 13:35 ` Christoph Hellwig
2026-07-02 13:47 ` Laurent Pinchart
2026-07-02 13:57 ` Lorenzo Stoakes
2026-07-02 14:09 ` Christian Brauner
2026-07-02 14:46 ` Lorenzo Stoakes
2026-07-02 16:18 ` Christian Brauner
2026-07-02 16:29 ` Lorenzo Stoakes
2026-07-02 8:08 ` Laurent Pinchart
2026-07-02 8:28 ` Christian Brauner
2026-07-02 13:48 ` Carlos Maiolino
2026-07-02 9:24 ` Lorenzo Stoakes
2026-07-01 18:35 ` Jeff Layton
2026-07-01 18:53 ` Jakub Kicinski
2026-07-02 7:29 ` Christian Brauner
2026-07-02 7:28 ` Christian Brauner
2026-07-02 8:12 ` Jori Koolstra
2026-07-02 8:44 ` Vlastimil Babka (SUSE)
2026-07-02 9:09 ` Jori Koolstra
2026-07-02 9:39 ` Lorenzo Stoakes
2026-07-02 9:37 ` Lorenzo Stoakes
2026-07-02 9:38 ` Laurent Pinchart
2026-07-02 9:44 ` Lorenzo Stoakes
2026-07-02 11:57 ` Brian Foster
2026-07-02 12:18 ` Lorenzo Stoakes
2026-07-02 13:07 ` Laurent Pinchart
2026-07-02 13:37 ` Lorenzo Stoakes
2026-07-02 13:47 ` Jori Koolstra
2026-07-02 13:09 ` Brian Foster
2026-07-02 13:25 ` Lorenzo Stoakes
2026-07-02 10:34 ` Krzysztof Kozlowski
2026-07-02 12:23 ` Lorenzo Stoakes
2026-07-02 12:39 ` Krzysztof Kozlowski
2026-07-02 12:53 ` Lorenzo Stoakes
2026-07-02 13:23 ` Laurent Pinchart
2026-07-02 10:27 ` Krzysztof Kozlowski
2026-07-02 11:27 ` Christoph Hellwig
2026-07-02 13:40 ` Carlos Maiolino
2026-07-03 9:21 ` Ellie
2026-07-03 11:58 ` Laurent Pinchart
2026-07-15 12:11 ` [PATCH RFC] coding-assistants: simplify attribution - WIPO recommendations also seem kind of worrying Ellie
[not found] ` <20f91215-f0db-4bb5-9ada-f3df33d78534@gmx.net>
2026-07-07 18:55 ` ckadr1 [this message]
2026-07-07 19:03 ` [PATCH RFC] coding-assistants: simplify attribution 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=5a789547-5c7c-488f-ad5f-3642c6c36d6b@gmx.net \
--to=ckadr1@gmx.net \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=jlayton@kernel.org \
--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