Comment by zahlman
2 days ago
Did the other Rust devs not manage to raise the same argument, repeatedly? It comes across that there must have been a massive breakdown in communication and it's hard for me to grok why.
2 days ago
Did the other Rust devs not manage to raise the same argument, repeatedly? It comes across that there must have been a massive breakdown in communication and it's hard for me to grok why.
There continues to be a vocal contingent of commenters (both here on HN, and elsewhere) who patiently listen to one side of the argument but put no stock whatsoever in what the R4L maintainers and contributors have to say on the subject.
> Did the other Rust devs not manage to raise the same argument, repeatedly?
Here are parts of a mail from Danilo Krummrich [1] in the thread that started all of this:
> As explained previously, this component is just a user of the DMA coherent allocator API (just like any other driver)
> Being a maintainer myself, I think it is outside the scope of a maintainer to restrict the usage of a public kernel API for a certain entity arbitrarily and / or by personal preference, which, as it appears to me, is the case here.
Emphasis is mine. This shows that the point was repeatedly raised. You can see for yourself what the response was. Besides, the only way to miss that point is to not look at the patch at all.
[1] https://lore.kernel.org/lkml/Z5qeoqRZKjiR1YAD@pollux/
It was indeed brought up.