惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
M
MIT News - Artificial intelligence
博客园 - Franky
J
Java Code Geeks
V
Visual Studio Blog
G
Google Developers Blog
罗磊的独立博客
MongoDB | Blog
MongoDB | Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Recent Announcements
Recent Announcements
Last Week in AI
Last Week in AI
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Stack Overflow Blog
Stack Overflow Blog
博客园 - 司徒正美
The GitHub Blog
The GitHub Blog
腾讯CDC
阮一峰的网络日志
阮一峰的网络日志
V
V2EX
博客园 - 【当耐特】
IT之家
IT之家
I
InfoQ
U
Unit 42
C
Check Point Blog
Martin Fowler
Martin Fowler

LWN.net comments

tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review? A reasonably extreme point of view [LWN.net]
Details of disclosure [LWN.net]
mvollrath · 2026-06-19 · via LWN.net comments

If one were to follow the kernel's LLM guidelines, that's not the information being offered. If I do 90% of the work and the LLM does 10% of the work, I Sign-off Assisted-by the LLM. If the LLM does 100% of the work, I Sign-off Assisted-by the LLM. These are a world apart wrt judging confidence in both the committer and the commits. At face value, you're lumping somebody who took the time to use a /kreview skill to check their work at the end together with somebody who was entirely hands off and couldn't pass a quiz about their commit.

As someone who genuinely wants both to learn how to work on the kernel and to use LLM tools responsibly, I don't want to look like a bot at a glance. Meanwhile the actual bots can just lie. So I don't think it's that obvious. If the policy is "you have to voluntarily add this mark of shame if you used a particular type of tool" then it's not likely to benefit anyone in such an obvious way. As we can see in the comments here, developers have all kinds of moral agendas which may conflict with the imperatives of the maintainers they are working with. The SFC's attempt at an ethical treatise is apparently not yet the final word.

And I don't want to dismiss the very real moral and ethical questions surrounding LLM technology and the way it is being rolled out. In our community the maintainers are the ones feeling the most pain, so I feel like the best course of action is to do whatever small change they ask me to do, for now, because my ethics bone tells me that these software projects continuing to be well-maintained is more important than hand wringing over mentioning the name of a company whose product I use while holding my nose.

From Corbet's 7.1 release statistics article:

> This release saw the merging of 15,849 non-merge changesets from 2,479 developers.

> The 7.1 cycle continued that trend [of first-time kernel contributors] with 530 new contributors [...]

> There are 299 commits in 7.1 that include an Assisted-by tag indicating the use of such a tool. The number of actual commits created with LLM involvement must be significantly higher, though; a number of developers are clearly not complying with the kernel's rules for disclosing that use.