Am 15.12.2014 um 19:56 schrieb Greg KH: > On Mon, Dec 15, 2014 at 10:41:03AM -0800, Greg KH wrote: >> On Mon, Dec 15, 2014 at 10:39:15AM -0800, Christoph Hellwig wrote: >>> On Mon, Dec 15, 2014 at 07:23:35PM +0100, Richard Weinberger wrote: >>>> I don't understand this kind of logic. >>>> a) Binder is considered a piece of shite. >>>> b) Google is working on a (hopefully sane) replacement. >>>> >>>> Why moving it out of staging then? What is the benefit? >>> >>> There is none, and Greg didn't even bother addressing the various >>> comments when this first came up. >> >> I thought I did, it was a long thread at the time, and I was on the road >> for 3 weeks, sorry if I missed something. >> >>> So a clear NAK from me on this one. >> >> You don't have to maintain it, I do, so why does it concern you? > > Ok, that was a bit snotty on my part, I apologize. > > But really, this is self-contained, doesn't touch any core > infrastructure, and is really just like any other driver for hardware > that people don't use. It shouldn't affect anything elsewhere in the > kernel, so objecting to it seems odd to me. Doesn't it use internal stuff from fs/file.c? Anyway, Linus pulled it. I'm just a bit astonished that binder finally sneaked into the core kernel. Hopefully no smart ass will ever decide to make some userspace component hard depend on it... Thanks, //richard _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
