From: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Oren Laadan <orenl-3AfRa/s5aFdBDgjK7y7TUQ@public.gmane.org>
Cc: "Linux Containers"
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Arve Hjønnevåg" <arve-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
"Eric Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
lxc-devel
<lxc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH 2/2] binder: implement namepsace support for Android binder driver
Date: Wed, 8 Jan 2014 15:49:28 -0800 [thread overview]
Message-ID: <20140108234928.GA20259@kroah.com> (raw)
In-Reply-To: <45c5d62a35f19228a681f5be9834741baabfdb0d.1387706794.git.orenl-3AfRa/s5aFdBDgjK7y7TUQ@public.gmane.org>
On Sun, Dec 22, 2013 at 05:07:40AM -0500, Oren Laadan wrote:
> Add namespaces support for the Android binder driver.
> As binder is an IPC mechanism, tie its namespace to IPC_NS.
Why does binder need namespace support?
Does the Android userspace code support this?
I need an ack from the Android developers before I can take this.
Same goes for the ipc core changes, I need an ack from the maintainer of
that code before I can take it as well.
thanks,
greg k-h
prev parent reply other threads:[~2014-01-08 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 10:07 [PATCH 0/2] Namespace support for Android binder (under ipc-ns) Oren Laadan
[not found] ` <cover.1387706794.git.orenl-3AfRa/s5aFdBDgjK7y7TUQ@public.gmane.org>
2013-12-22 10:07 ` [PATCH 1/2] ipc namespace: a generic per-ipc pointer and peripc_ops Oren Laadan
2013-12-22 10:07 ` [PATCH 2/2] binder: implement namepsace support for Android binder driver Oren Laadan
[not found] ` <45c5d62a35f19228a681f5be9834741baabfdb0d.1387706794.git.orenl-3AfRa/s5aFdBDgjK7y7TUQ@public.gmane.org>
2013-12-22 10:38 ` Stefan Beller
2014-01-08 23:49 ` Greg Kroah-Hartman [this message]
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=20140108234928.GA20259@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=arve-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lxc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=orenl-3AfRa/s5aFdBDgjK7y7TUQ@public.gmane.org \
/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