Add new maintainers for ashmem driver to handle related issues.
Signed-off-by: Suren Baghdasaryan <[email protected]>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1d4aa7f942de..8b2f139b196d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1170,6 +1170,8 @@ M: Todd Kjos <[email protected]>
M: Martijn Coenen <[email protected]>
M: Joel Fernandes <[email protected]>
M: Christian Brauner <[email protected]>
+M: Hridya Valsaraju <[email protected]>
+M: Suren Baghdasaryan <[email protected]>
L: [email protected]
S: Supported
T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
--
2.27.0.383.g050319c2ae-goog
On Wed, Jul 08, 2020 at 04:12:53PM -0700, Suren Baghdasaryan wrote:
> Add new maintainers for ashmem driver to handle related issues.
>
> Signed-off-by: Suren Baghdasaryan <[email protected]>
Can I get an ack/reviewed-by/something by the existing maintainers to
verify this? :)
And I thought we were deleting ashmem soon?
thanks,
greg k-h
On Thu, Jul 9, 2020 at 4:18 AM Greg KH <[email protected]> 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.
On Thu, Jul 09, 2020 at 09:03:13AM -0400, Joel Fernandes wrote:
> On Thu, Jul 9, 2020 at 4:18 AM Greg KH <[email protected]> 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.
On Thu, Jul 9, 2020 at 1:18 AM Greg KH <[email protected]> wrote:
>
> On Wed, Jul 08, 2020 at 04:12:53PM -0700, Suren Baghdasaryan wrote:
> > Add new maintainers for ashmem driver to handle related issues.
> >
> > Signed-off-by: Suren Baghdasaryan <[email protected]>
Acked-by: Todd Kjos <[email protected]>
>
> Can I get an ack/reviewed-by/something by the existing maintainers to
> verify this? :)
>
> And I thought we were deleting ashmem soon?
>
> thanks,
>
> greg k-h