From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753278AbdG1Xsh (ORCPT ); Fri, 28 Jul 2017 19:48:37 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:59718 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752987AbdG1Xsg (ORCPT ); Fri, 28 Jul 2017 19:48:36 -0400 Date: Fri, 28 Jul 2017 16:22:52 -0700 From: Greg KH To: Martijn Coenen Cc: john.stultz@linaro.org, tkjos@google.com, arve@android.com, amit.pundir@linaro.org, linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org, maco@google.com Subject: Re: [PATCH 0/3] ANDROID: binder: reconcile with android common tree Message-ID: <20170728232252.GA29333@kroah.com> References: <20170728115608.61306-1-maco@android.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170728115608.61306-1-maco@android.com> User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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