[PATCH] staging: android: binder: move to the "real" part of the kernel

John Stultz john.stultz at linaro.org
Thu Oct 16 17:09:04 UTC 2014

On Thu, Oct 16, 2014 at 5:47 AM, Greg Kroah-Hartman
<gregkh at linuxfoundation.org> wrote:
> From: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
> The Android binder code has been "stable" for many years now.  No matter

Well, ignoring the ABI break that landed in the last year. :)

> 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.
> Signed-off-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
> ---
> This was discussed in the Android miniconf at the Plumbers conference.
> If anyone has any objections to this, please let me know, otherwise I'm
> queueing this up for 3.19-rc1

So my main concerns/thoughts here are:

Who is going to maintain this? Has Arve agreed?  Are the Android guys
comfortable with the ABI stability rules they'll now face?  Currently
in the android space no one but libbinder should use the kernel
interface. Can we enforce that no one use this interface out-side of
android (To ensure its one of those "if the abi breaks and no one
notices..." edge cases)?

I'm still hopeful that a libbinder over kdbus will eventually pan out.
I still see having two core IPC mechanisms (even if the use cases are
different in style) as a negative, and I worry this might reduce
motivation to unify things at the lower level. Granted, such work can
still continue, but the incentives do change.


More information about the devel mailing list