Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20200708231253.3831497-1-surenb@google.com> <20200709081820.GB13487@kroah.com>
In-Reply-To: <20200709081820.GB13487@kroah.com>
From:   Joel Fernandes <joel@joelfernandes.org>
Date:   Thu, 9 Jul 2020 09:03:13 -0400
Message-ID: <CAEXW_YQ5VoN6DZcfJH_4u5MnRc0vybY7zYH3Y_WD=j3u-RRVHQ@mail.gmail.com>
Subject: Re: [PATCH 1/1] MAINTAINERS: add Hridya and myself into Android
 driver maintainers list
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     Suren Baghdasaryan <surenb@google.com>,
        Hridya Valsaraju <hridya@google.com>,
        Todd Kjos <tkjos@google.com>,
        Christian Brauner <christian@brauner.io>,
        =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= <arve@android.com>,
        Martijn Coenen <maco@android.com>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.