Re: [PATCH AUTOSEL 4.20 36/81] binder: fix CONFIG_ANDROID_BINDER_DEVICES

2019-03-11 Thread Sasha Levin
On Thu, Feb 28, 2019 at 04:24:07PM +0100, Greg Kroah-Hartman wrote: On Thu, Feb 28, 2019 at 10:07:28AM -0500, Sasha Levin wrote: From: Christian Brauner [ Upstream commit 793c8232937610ae00bc174b87d7fc324346eaea ] Several users have tried to only rely on binderfs to provide binder devices and

Re: [PATCH AUTOSEL 4.20 36/81] binder: fix CONFIG_ANDROID_BINDER_DEVICES

2019-02-28 Thread Greg Kroah-Hartman
On Thu, Feb 28, 2019 at 10:07:28AM -0500, Sasha Levin wrote: > From: Christian Brauner > > [ Upstream commit 793c8232937610ae00bc174b87d7fc324346eaea ] > > Several users have tried to only rely on binderfs to provide binder devices > and set CONFIG_ANDROID_BINDER_DEVICES="" empty. This is a grea

[PATCH AUTOSEL 4.20 36/81] binder: fix CONFIG_ANDROID_BINDER_DEVICES

2019-02-28 Thread Sasha Levin
From: Christian Brauner [ Upstream commit 793c8232937610ae00bc174b87d7fc324346eaea ] Several users have tried to only rely on binderfs to provide binder devices and set CONFIG_ANDROID_BINDER_DEVICES="" empty. This is a great use-case of binderfs and one that was always intended to work. However,