From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
Christian Brauner <brauner@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <axboe@kernel.dk>, Jeff Layton <jlayton@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Wed, 1 Jul 2026 18:12:25 +0200 [thread overview]
Message-ID: <eab184a0-7c25-4aec-be91-b5166c706c62@kernel.org> (raw)
In-Reply-To: <87jyreofpw.fsf@trenco.lwn.net>
>> I acknowledge that my stance is even more radical: imho we would just
>> stop it with any disclosure requirements completely. It's useless imho.
>> We already see that other than core contributors most people don't care
>> and will just not disclose their usage of AI.
>
> The widespread ignoring of the disclosure rule is, IMO, something we
> need to address somehow; were I still on the TAB, I'd be raising the
> issue there. Either we find a way to be serious about enforcing the
> disclosure rule, or we should just drop it. A rule that everybody
> ignores is less than useful.
Note. :)
We do have people using it, and at least in MM, when we suspect AI usage and get
the confirmation, we would tell people to use proper tags. (happens not so often
IIRC)
--
Cheers,
David
next prev parent reply other threads:[~2026-07-01 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 15:54 [PATCH RFC] coding-assistants: simplify attribution Christian Brauner
2026-07-01 16:08 ` Mark Brown
2026-07-01 16:08 ` Jonathan Corbet
2026-07-01 16:12 ` David Hildenbrand (Arm) [this message]
2026-07-01 16:10 ` David Hildenbrand (Arm)
2026-07-01 18:35 ` Jeff Layton
2026-07-01 18:53 ` Jakub Kicinski
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=eab184a0-7c25-4aec-be91-b5166c706c62@kernel.org \
--to=david@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--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