[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190815160029.GA23940@kroah.com>
Date: Thu, 15 Aug 2019 18:00:29 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Hridya Valsaraju <hridya@...gle.com>
Cc: Arve Hjønnevåg <arve@...roid.com>,
Todd Kjos <tkjos@...roid.com>,
Martijn Coenen <maco@...roid.com>,
Joel Fernandes <joel@...lfernandes.org>,
Christian Brauner <christian@...uner.io>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [PATCH v3 0/2] Add default binderfs devices
On Thu, Aug 08, 2019 at 03:27:24PM -0700, Hridya Valsaraju wrote:
> Binderfs was created to help provide private binder devices to
> containers in their own IPC namespace. Currently, every time a new binderfs
> instance is mounted, its private binder devices need to be created via
> IOCTL calls. This patch series eliminates the effort for creating
> the default binder devices for each binderfs instance by creating them
> automatically.
>
> Hridya Valsaraju (2):
> binder: Add default binder devices through binderfs when configured
> binder: Validate the default binderfs device names.
I'd like to get a reviewed-by from the other binder maintainers before
taking this series....
{hint}
Powered by blists - more mailing lists