[steveklabnik]

> The issue is that changing the DMA code will in turn potentially break the drivers written in Rust and the maintainer has no incentive to do that extra mile himself to make this not to happen.

He has no reason to do anything to make it not happen. He is 100% within his rights to ignore things entirely.

> Rust devs OTOH offer say "we're gonna help you fix it" but this obviously creates an extra technical and communication burden.

No, they say "we are going to fix it." He has no responsibility for Rust code. This is the terms of the experiment, which has been clear for years now.

> "xy DMA patch didn't manage to get into this release because we didn't manage to fix all the zy Rust dependencies".

This is not how the process works. All DMA patches get in, if the Rust is broken, it would be "The Rust code that depends on DMA did not get in this release."