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 <christian@xxxxxxxxxx>
[ 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, this is
currently not possible since setting CONFIG_ANDROID_BINDER_DEVICES="" emtpy
will simply panic the kernel:
There is no binderfs on 4.20, so this patch is not needed on anything
older than 5.0.
Please drop it from your queues.
Heh, I knew binder was there for a while, didn't know binderfs is
something new. Now dropped, thanks!
--
Thanks,
Sasha
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
