[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190128114729.GD1795@kadam>
Date: Mon, 28 Jan 2019 14:47:29 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Christian Brauner <christian@...uner.io>
Cc: gregkh@...uxfoundation.org, tkjos@...roid.com,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, arve@...roid.com,
Martijn Coenen <maco@...gle.com>, joel@...lfernandes.org,
maco@...roid.com, tkjos@...gle.com
Subject: Re: [PATCH] binder: fix CONFIG_ANDROID_BINDER_DEVICES
On Sat, Jan 26, 2019 at 11:23:20AM +0100, Christian Brauner wrote:
> 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:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It should just do a WARN() and not panic the kernel.
regards,
dan carpenter
Powered by blists - more mailing lists