Comment by kllrnohj
10 months ago
You should click through some of the links to see where the clashes actually happened. It didn't have anything to do with the actual hardware support. Rather, it was over stupid shit like the kernel DMA team throwing a hissy fit over the idea of there being Rust bindings for the DMA interface: https://lore.kernel.org/lkml/20250108122825.136021-3-abdiel....
When the response to such a small contribution is just "No rust code in kernel/dma, please" with a complete shutdown of any attempt to discuss alternatives, it's kinda pointless. Even though Rust is supposed to be an allowed language in the kernel now, with blessing from Linus himself, there's apparently just submaintainers of critical, highly shared infrasture that outright refuse it.
So this has nothing to do with "who will own the Apple drivers?!" but just the rest of the kernel going "your integration layers are an affront to our Holy C, begone religious heretics!"
"No rust code in kernel/dma, please" is a totally reasonable request though, once again it comes down to who supports it? When 99% of the kernel is written in C it makes sense to keep it C.
If you start introducing new languages that most maintainers are not anywhere near as familiar with, you create an unmaintainable mess.
Linux isn't a hobby project anymore, its critical infrastructure. You can just introduce changes because a few people think its cool.
Rust in Linux has official blessing. 99% of the kernel being in C is irrelevant, it's not a C-only kernel anymore officially.
But since the patch didn’t include any code in kernel/dma, it comes across as “I didn’t even read the patch.”