From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: [PATCH] staging: android: binder: move to the "real" part of the kernel Date: Fri, 17 Oct 2014 01:14:57 +0200 Message-ID: <20141016231457.GB13592@kroah.com> References: <20141016124741.GA3832@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" To: "Michael Kerrisk (man-pages)" Cc: devel@driverdev.osuosl.org, Anup Patel , Linux API , lkml , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Santosh Shilimkar , Rebecca Schultz Zavin , John Stultz , Sumit Semwal , Christoffer Dall List-Id: linux-api@vger.kernel.org On Thu, Oct 16, 2014 at 04:18:02PM +0200, Michael Kerrisk (man-pages) wrote: > On Thu, Oct 16, 2014 at 2:47 PM, Greg Kroah-Hartman > wrote: > > From: Greg Kroah-Hartman > > > > The Android binder code has been "stable" for many years now. No matter > > what comes in the future, we are going to have to support this API, so > > might as well move it to the "real" part of the kernel as there's no > > real work that needs to be done to the existing code. > > Where does one find the canonical documentation of the user-space API? There really is only one "canonical" thing, and that is in the libbinder code in the Android userspace repository. And it's not really "documentation" so much as, "a C file that interacts with the ioctls in the binder kernel code" :( Think of this as just a random character driver with some funny ioctls that will never get really documented as there is only one user of it. sorry, greg k-h