binderfs: remove separate device_initcall()
authorChristian Brauner <christian@brauner.io>
Thu, 31 Jan 2019 00:25:02 +0000 (01:25 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 1 Feb 2019 14:50:26 +0000 (15:50 +0100)
commit5b9633af298bfd1de650f6774d3fada546543101
tree33e1fa97ac4e8f80cd906d487c7e42cb5addc54b
parent32a66374487bbd78115747f0084cea5e8fca4c80
binderfs: remove separate device_initcall()

binderfs should not have a separate device_initcall(). When a kernel is
compiled with CONFIG_ANDROID_BINDERFS register the filesystem alongside
CONFIG_ANDROID_IPC. This use-case is especially sensible when users specify
CONFIG_ANDROID_IPC=y, CONFIG_ANDROID_BINDERFS=y and
ANDROID_BINDER_DEVICES="".
When CONFIG_ANDROID_BINDERFS=n then this always succeeds so there's no
regression potential for legacy workloads.

Signed-off-by: Christian Brauner <christian@brauner.io>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/android/binder.c
drivers/android/binder_internal.h
drivers/android/binderfs.c