On Mon, Oct 20, 2014 at 06:04:50AM +0800, Greg Kroah-Hartman wrote: > There is now work to resolve the interface, it requires someone who has > the rights to push to Android userspace. But that is going to be a > "total rewrite", and until then, this code needs to be used, no matter > how much we hate this. It helps to qualify why it absolutely has to, and why this is different from other interfaces we haven't merged. Is this the last building block to run upstream Linux on a common Android device out of the box without needing any patches or out of tree drivers? Is there any other good reason I might have missed. To convince other people that merging a piece like this absolutely needs to get merged I'd suggest you start with presenting factual argument, and then let the broader audience weight their merrits. I think with the known problems of the code, and the fact that the real user ABI is a library anyway the stakes are quite high here. So as a start please prepare a list of arguments, a detailed description of the ABI, and post a proper patch (not a move) that suggests adding this driver to all the relevant lists (most importantly linux-fsdevel and linux-api) so that people with the right experience can review it. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
