On Fri, Jul 28, 2017 at 01:56:05PM +0200, Martijn Coenen wrote: > When comparing the android common kernel branch with > upstream, I found several differences. > > The "add padding" patch has long been applied in common, > and shipping versions of Android userspace depends on this > particular alignment; so while it does change UAPI, we > have never shipped a userspace that used the old UAPI, > so this change does not break anything. > > The "add hwbinder,vndbinder" patch changes the default > binder device nodes to match what the latest Android > userspace (O) requires. > > Finally, the recent patch-stack for fine-grained locking > contained a patch that for some reason was incomplete; > "fix proc->tsk check" addresses this particular problem. Ok, do some of these need to go to Linus now for 4.13-final and to the stable trees to match up with the 3 that are already proposed for the stable trees? If so, which ones? thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
