summaryrefslogtreecommitdiffstats
path: root/drivers/android/binder_internal.h
diff options
context:
space:
mode:
authorChristian Brauner <christian@brauner.io>2019-01-31 01:25:02 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-02-01 15:50:26 +0100
commit5b9633af298bfd1de650f6774d3fada546543101 (patch)
tree33e1fa97ac4e8f80cd906d487c7e42cb5addc54b /drivers/android/binder_internal.h
parentfpga: stratix10-soc: fix wrong of_node_put() in init function (diff)
downloadlinux-5b9633af298bfd1de650f6774d3fada546543101.tar.xz
linux-5b9633af298bfd1de650f6774d3fada546543101.zip
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>
Diffstat (limited to 'drivers/android/binder_internal.h')
-rw-r--r--drivers/android/binder_internal.h9
1 files changed, 9 insertions, 0 deletions
diff --git a/drivers/android/binder_internal.h b/drivers/android/binder_internal.h
index 7fb97f503ef2..045b3e42d98b 100644
--- a/drivers/android/binder_internal.h
+++ b/drivers/android/binder_internal.h
@@ -46,4 +46,13 @@ static inline bool is_binderfs_device(const struct inode *inode)
}
#endif
+#ifdef CONFIG_ANDROID_BINDERFS
+extern int __init init_binderfs(void);
+#else
+static inline int __init init_binderfs(void)
+{
+ return 0;
+}
+#endif
+
#endif /* _LINUX_BINDER_INTERNAL_H */