From: Christian Brauner <christian.brauner@ubuntu.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Hridya Valsaraju" <hridya@google.com>,
"Todd Kjos" <tkjos@google.com>,
"Christian Brauner" <christian@brauner.io>,
"Arve Hjønnevåg" <arve@android.com>,
"Martijn Coenen" <maco@android.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] MAINTAINERS: add Hridya and myself into Android driver maintainers list
Date: Thu, 9 Jul 2020 15:09:24 +0200 [thread overview]
Message-ID: <20200709130924.alkcskho5miybvd2@wittgenstein> (raw)
In-Reply-To: <CAEXW_YQ5VoN6DZcfJH_4u5MnRc0vybY7zYH3Y_WD=j3u-RRVHQ@mail.gmail.com>
On Thu, Jul 09, 2020 at 09:03:13AM -0400, Joel Fernandes wrote:
> On Thu, Jul 9, 2020 at 4:18 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > And I thought we were deleting ashmem soon?
>
> This seems harder than initially thought. The Android userspace is
> intertwined with ashmem in various ways (security policies, apps etc).
> There were various concerns with old apps using /dev/ashmem directly
> without going through library layers and that such apps could not be
> upgraded. Various approaches were tried to work around this by
> different folks to varying degrees of effect. Also, I am no longer
> with the Android team at Google, but I continue to work with them
> upstream.
>
> Fwiw, I will continue reviewing this and other Android code from my
> side. Thanks.
Same.
next prev parent reply other threads:[~2020-07-09 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 23:12 Suren Baghdasaryan
2020-07-09 8:18 ` Greg KH
2020-07-09 13:03 ` Joel Fernandes
2020-07-09 13:09 ` Christian Brauner [this message]
2020-07-09 15:47 ` Todd Kjos
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=20200709130924.alkcskho5miybvd2@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=surenb@google.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®