The dma maintainer wants all the code he’s in charge of to be stuff he likes to work with. Whether you agree with that or not, that has absolutely nothing to do with Linus Torvalds allowing more rust code in the kernel.
They were trying to merge rust code into the dma subsystem, because what they were working on needed to talk to it, and it would be easier to do that with rust code in the dma subsystem. He said no specifically to that part. Just the stuff in the dma subsystem. That’s all. It can be worked around.
It wasn’t actually a big deal until Martin stuck his nose into a discussion that was none of his business and then cried about it on social media. I get being frustrated. The old guys are weirdly hostile sometimes, but creating drama is not the solution.
Well, the rust devs are trying to add more rust code, and the dma maintainer rejected it because it was was written in rust. Thus, the question.
The dma maintainer wants all the code he’s in charge of to be stuff he likes to work with. Whether you agree with that or not, that has absolutely nothing to do with Linus Torvalds allowing more rust code in the kernel.
That’s the thing though, he’s not in charge of this code.
The lone dma maintainer isn’t in charge of the code in the dma subsystem? What do you even mean by that?
He’s not in charge of the rust code they want to merge. They asked him about it because their code talks with the dma system.
They were trying to merge rust code into the dma subsystem, because what they were working on needed to talk to it, and it would be easier to do that with rust code in the dma subsystem. He said no specifically to that part. Just the stuff in the dma subsystem. That’s all. It can be worked around.
It wasn’t actually a big deal until Martin stuck his nose into a discussion that was none of his business and then cried about it on social media. I get being frustrated. The old guys are weirdly hostile sometimes, but creating drama is not the solution.