Skip to contentSkip to conversation

MAINTAINERS: add Hridya and myself into Android driver maintainers list

PATCH In review Suren Baghdasaryan 5 participants 5 messages Jul 8, 2020 – Jul 9, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: add Hridya and myself into Android driver maintainers list

Add new maintainers for ashmem driver to handle related issues.

---
 MAINTAINERS | 2 ++
 1 file changed, 2 insertions(+)
MAINTAINERS +2 -0
index 1d4aa7f942de..8b2f139b196d 100644
@@ -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
Signature · 1 line
2.27.0.383.g050319c2ae-goog
#1 lore raw
Quoted 3 lines · Suren Baghdasaryan

Add new maintainers for ashmem driver to handle related issues.

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

#2 lore raw
Quoted 1 line · Greg KH

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.

#3 lore raw
Quoted 12 lines · Joel Fernandes
Quoted 1 line · Greg KH

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.

Quoted 2 lines

Fwiw, I will continue reviewing this and other Android code from my side. Thanks.

Same.