From: Christian Brauner <christian@brauner.io>
To: "chouryzhou(周威)" <chouryzhou@tencent.com>
Cc: "Todd Kjos" <tkjos@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
LKML <linux-kernel@vger.kernel.org>,
"Arve Hjønnevåg" <arve@android.com>,
"joel@joelfernandes.org" <joel@joelfernandes.org>,
"darrick.wong@oracle.com" <darrick.wong@oracle.com>,
"david@fromorbit.com" <david@fromorbit.com>,
"kilobyte@angband.pl" <kilobyte@angband.pl>,
"open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH v1] binder: implement binderfs(Internet mail)
Date: Tue, 11 Dec 2018 06:54:56 +0100 [thread overview]
Message-ID: <20181211055455.lb55hto554klzdvf@brauner.io> (raw)
In-Reply-To: <5FBCBE569E134E4CA167B91C0A77FD610198FD6A14@EXMBX-SZMAIL022.tencent.com>
On Tue, Dec 11, 2018 at 03:44:48AM +0000, chouryzhou(周威) wrote:
> > chouryzhou@, can you confirm that this implementation works for your
> > android-in-container use-case?
> >
> > -Todd
> >
> We are running Android Pie in container now. If it works for later Android
> release, it will works for us.
The patchset is absolutely agnostic as to what Android version is
running. :) It has no userspace consequences.
If at all it makes it possible for Android to upgrade its userspace to
use additional devices in the future without having to recompile the
kernel. There's a whole lot of interesting things one could potentially
do with this. :)
next prev parent reply other threads:[~2018-12-11 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 23:25 [PATCH v1] binder: implement binderfs Christian Brauner
2018-12-10 17:50 ` Todd Kjos
2018-12-11 3:44 ` [PATCH v1] binder: implement binderfs(Internet mail) chouryzhou(周威)
2018-12-11 5:54 ` Christian Brauner [this message]
2018-12-12 12:51 ` [PATCH v1] binder: implement binderfs Christian Brauner
2018-12-12 17:54 ` Todd Kjos
2018-12-13 17:56 ` Greg Kroah-Hartman
2018-12-13 20:52 ` Christian Brauner
2018-12-13 21:13 ` Greg Kroah-Hartman
2018-12-13 16:44 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181211055455.lb55hto554klzdvf@brauner.io \
--to=christian@brauner.io \
--cc=arve@android.com \
--cc=chouryzhou@tencent.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=tkjos@android.com \
--cc=tkjos@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®