undefined | Better HN

0 pointssteveklabnik1y ago0 comments

> (to the extend this is the case, I haven't checked)

It's not his area.

> Also the patch adds a file kernel/dma.rs so I am confused about your comment.

It adds rust/kernel/dma.rs, not kernel/dma. That is, it adds that file here: https://github.com/torvalds/linux/tree/master/rust/kernel not here: https://github.com/torvalds/linux/tree/master/kernel/dma

0 comments

uecker1y ago

If it is not his area, he should have no power to stop it anyway, so it is even more strange to call it "sabotage". Or has any kernel developer the right to nack anything? This seems unlikely to me. So then it is just some disagreement.

steveklabnikOP1y ago

You have to remember that Linux development isn't done like most open source projects where there's one upstream tree everyone sends patches to. Linus pulls in whatever code he wants. A nack means that Hellwig won't pull it into his tree, but that doesn't mean it can't go in someone else's, and end up upstream anyway. The only reason he was even cc'd on the patch is because he's the relevant subsystem maintainer being wrapped, as a courtesy.

uecker1y ago

As I said, the idea that this is then "sabotage" is completely ridiculous and just shows how toxic this maintainer was that now removed himself.

1 more reply

j / k navigate · click thread line to collapse

0 pointssteveklabnik1y ago0 comments

> (to the extend this is the case, I haven't checked)

It's not his area.

> Also the patch adds a file kernel/dma.rs so I am confused about your comment.

0 comments

uecker1y ago

steveklabnikOP1y ago

uecker1y ago

As I said, the idea that this is then "sabotage" is completely ridiculous and just shows how toxic this maintainer was that now removed himself.

1 more reply

j / k navigate · click thread line to collapse