The linux-media mailing list exists to argue about camera drivers. On Wednesday it settled something bigger. Linus Torvalds, responding to contributors who "really dislike AI," put his foot down as top-level maintainer: "Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away." The kernel — the most reviewed, most conservative, most load-bearing codebase in the world — now has an AI policy. It took three sentences.
The ruling is narrower than the headline reading, and more interesting. Torvalds didn't declare AI-generated code good, or safe, or welcome by default. He declared the categorical objection dead: "AI is a tool, just like other tools we use." He didn't settle quality. He settled jurisdiction. From now on, an objection to a patch has to be about the patch.
It may not have been that "clearly" even just a year ago, but it's no longer in question today. There are other questions around AI (like what the economy of it will actually look like in the end), but "is it useful" is no longer one of those questions. Anybody who doubts that clearly hasn't actually used it.Linus Torvalds, linux-media mailing list
Notice the sorting. Usefulness: closed. Economics: open. The ordering matters because of who is doing it. Torvalds has no model to sell and no fund exposure to AI labs; his public record is thirty-five years of calling bad code garbage, loudly, whoever wrote it. Nobody on earth has more standing to reject AI on craft grounds. He declined.
He didn't settle quality. He settled jurisdiction.
There's a structural point buried in "fork it or walk away." Open source has spent two years tearing at this — projects writing bans on AI-generated contributions, maintainers drowning in machine-generated bug reports, flame wars re-litigating the tool on every patch that smells synthetic. Most projects govern by consensus, so the argument never ends. The kernel has a person. A foundation would have chartered a working group and shipped a policy PDF next spring. Linux resolved it in an email, because thirty-five years of being mostly right about the project is a kind of authority you can spend. On Wednesday, Torvalds spent some.
The honest objection: a green light from the top is how maintainers end up buried in confident-looking slop, and fiat doesn't make any of it good. The volume problem is real, and the review load lands on subsystem maintainers who didn't choose the policy. But the kernel's filter was never a policy about tools. It is named maintainers with taste saying no, patch by patch, for any reason they can defend. That filter survives Wednesday intact. What's gone is the shortcut — rejecting the tool so you never have to judge the work.
Everyone else is still litigating the tool. The kernel just went back to litigating the code.