Christian Brauner 5b9633af29 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>		2019-02-01 15:50:26 +01:00
..
binder.c	binderfs: remove separate device_initcall()	2019-02-01 15:50:26 +01:00
binder_alloc.c	Merge 4.20-rc5 into char-misc-next	2018-12-03 07:56:15 +01:00
binder_alloc.h	binder: fix kerneldoc header for struct binder_buffer	2018-12-06 15:44:14 +01:00
binder_alloc_selftest.c
binder_internal.h	binderfs: remove separate device_initcall()	2019-02-01 15:50:26 +01:00
binder_trace.h	binder: use standard functions to allocate fds	2018-09-14 15:22:36 +02:00
binderfs.c	binderfs: remove separate device_initcall()	2019-02-01 15:50:26 +01:00
Kconfig	binder: implement binderfs	2018-12-19 09:40:13 +01:00
Makefile	binder: implement binderfs	2018-12-19 09:40:13 +01:00