From: Christoph Hellwig <hch@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
devel@driverdev.osuosl.org, "Todd Kjos" <tkjos@android.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"John Stultz" <john.stultz@linaro.org>,
"Martijn Coenen" <maco@android.com>
Subject: Re: [PATCH] android: binder: fix type mismatch warning
Date: Mon, 18 Sep 2017 08:52:06 -0700 [thread overview]
Message-ID: <20170918155206.GD16672@infradead.org> (raw)
In-Reply-To: <CAK8P3a0_dOue+3jYaH3PNNvur7gpMaAVOm5MHfrZykj+3Z0Saw@mail.gmail.com>
On Mon, Sep 18, 2017 at 05:35:03PM +0200, Arnd Bergmann wrote:
> Probably not on a native Android device or even a Chromebook that
> ships a binder user space together with a kernel, but what about
> people using "anbox" or similar projects that allow you to run
> Android apps in a container?
>
> It seems like a legitimate use case of the binder modules, but
> now there is a kernel Kconfig option that has to match a user
> space binary.
Agreed. It's also against our general policy for userspace interfaces.
next prev parent reply other threads:[~2017-09-18 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 8:56 [PATCH] android: binder: fix type mismatch warning Arnd Bergmann
2017-09-18 14:02 ` Greg Kroah-Hartman
2017-09-18 15:35 ` Arnd Bergmann
2017-09-18 15:52 ` Christoph Hellwig [this message]
2017-09-18 15:53 ` Greg Kroah-Hartman
2017-09-18 16:23 ` Christoph Hellwig
2017-09-18 16:33 ` Greg Kroah-Hartman
2017-09-18 19:49 ` Arnd Bergmann
2017-09-20 9:08 ` Martijn Coenen
2017-09-20 9:58 ` Arnd Bergmann
2017-09-20 10:24 ` Martijn Coenen
2017-09-20 13:37 ` Arnd Bergmann
2017-09-21 7:44 ` Greg Kroah-Hartman
2017-09-22 7:00 ` Martijn Coenen
2017-09-22 9:12 ` Arnd Bergmann
2017-09-22 12:46 ` Martijn Coenen
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=20170918155206.GD16672@infradead.org \
--to=hch@infradead.org \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=riandrews@android.com \
--cc=tkjos@android.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