Comment by db48x

> I do not believe that it will be possible for "the Rust for Linux team to step in and make whatever changes to the Rust code are needed", because that is much easier said than done.

No, certainly not forever. In the short term I think it is a workable solution. I think that over time more and more maintainers will realize that maintaining Rust code is easier than maintaining C code, and that there is actually very little added burden to maintaining the Rust bindings and abstractions that wrap their C code. The Thus the Rust team will not have to do that job forever.

> Whoever changes an interface should also have the obligation to write a concise migration guide in which to explain what must be done to convert the invocations of the old interfaces into invocations of the new interfaces.

That is an excellent suggestion :)

The migration guide should be part of, or even the bulk of, a well–written commit message.

> However, there have been some Linux developers who not only did not make easy the maintaining of out-of-kernel device drivers, but who have made efforts to make as difficult as possible the maintaining of out-of-kernel device drivers, apparently due to some misguided belief that this will hurt some evil corporations.

And that doesn’t surprise me at all.