On Mon, Feb 10, 2025 at 05:41:30PM +0800, Icenowy Zheng wrote: > Furtherly, the monorepo nature of Linux kernel means to refactor an > interface, it's usually the person changing the callee that need to > change all callers to satify the interface change; having Rust code in > tree calling the interface effectively means adding the responsibility > of fixing the Rust code when the interface changes, which could be not > acceptable by the C-only maintainers. In regards of adding a > maintainer, having more maintainers means more communication. This is exactly the same as for every new driver / component, regardless of whether it is written in C or in Rust. It is absolutely common that driver maintainers help with integrating core API changes, if necessary. I don't see why the same process should not work for Rust abstractions. (Additionally, in this particular case even one of the reviewers of DMA MAPPING HELPERS offered to be a reviewer of the Rust abstractions too, in order to keep eye on the DMA API angle.)
