this post was submitted on 14 Oct 2026
58 points (90.3% liked)

Fuck AI

8473 readers
879 users here now

"We did it, Patrick! We made a technological breakthrough!"

A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.

AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.

founded 2 years ago
MODERATORS
 

A few days after Micro$lop announced they're using AI to develop Windows, PCs with Win11 started to have a bug, where the screen goes black (usually no signal), then the GUI slowly crawls back to be visible one-by-one. I wonder what kind of Linux equivalent we will have.

you are viewing a single comment's thread
view the rest of the comments
[–] sem@piefed.blahaj.zone 4 points 2 days ago
The Maintainers Summit reached consensus to deprecate the Assisted-by
tag. Remove the documentation requiring it.

Signed-off-by: Sasha Levin <sashal@kernel.org>


Documentation/process/coding-assistants.rst | 21 +------------------ Documentation/process/submitting-patches.rst | 10 --------- .../it_IT/process/submitting-patches.rst | 10 --------- scripts/checkpatch.pl | 11 ---------- 4 files changed, 1 insertion(+), 51 deletions(-)

diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst index 051f0d819f68e..509dbf23a099b 100644


a/Documentation/process/coding-assistants.rst

+++ b/Documentation/process/coding-assistants.rst @@ -40,24 +40,6 @@ is responsible for:

  • Adding their own Signed-off-by tag to certify the DCO
  • Taking full responsibility for the contribution

-Attribution -===========

-When AI tools contribute to kernel development, proper attribution -helps track the evolving role of AI in the development process. -Contributions should include an Assisted-by tag in the following format::

  • Assisted-by: LLM [TOOL1] [TOOL2]

-* [TOOL1] [TOOL2] are optional specialized analysis tools used

  • (e.g., coccinelle, sparse, smatch, clang-tidy)

-Basic development tools (git, gcc, make, editors) should not be listed.

-Example::

  • Assisted-by: LLM coccinelle sparse

Procedure for finding and fixing bugs

@@ -82,8 +64,7 @@ these steps: another one. The fix must not add build warnings and must pass the checkpatch.pl checks (see submitting-patches.rst). 6. Commit the working fix with a detailed message describing the problem, the

  • solution and a Fixes tag. Do not add a Signed-off-by tag, and add an
  • Assisted-by tag, as described above.
  • solution and a Fixes tag. Do not add a Signed-off-by tag.
  1. Identify the maintainers and lists using scripts/get_maintainer.pl. Documentation/process/security-bugs.rst shows how to do that.
  2. Indicate what could not be done. If the fix could not be built or tested, or diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index 7ae79452e1b46..5f4e0156cca78 100644

a/Documentation/process/submitting-patches.rst

+++ b/Documentation/process/submitting-patches.rst @@ -632,16 +632,6 @@ bugzilla.kernel.org is a public place in this sense, but email addresses used there are private; so do not expose them in tags, unless the person used them in earlier contributions.

-Using Assisted-by:

-If you used any sort of advanced coding tool in the creation of your patch, -you need to acknowledge that use by adding an Assisted-by tag. Failure to -do so may impede the acceptance of your work. Please see -Documentation/process/coding-assistants.rst for details regarding the -acknowledgment of coding assistants.

.. _the_canonical_patch_format:

The canonical patch format diff --git a/Documentation/translations/it_IT/process/submitting-patches.rst b/Documentation/translations/it_IT/process/submitting-patches.rst index a742610cb0709..d0e0d6c9ecc2e 100644