Add default binderfs devices
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest2 patches 15 repliesIn review
- v22 patches 4 repliesSuperseded
- v11 patch 3 repliesSuperseded
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | binder: Add default binder devices through binderfs when configureddrivers/ drivers/ drivers/ | +25 | 5 replies | |
| 2/2 | binder: Validate the default binderfs device names.drivers/ | +12 | 9 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Joel Fernandes (Google) |
|---|---|
| Series | R-b R-b |
| 1/2 | R-b R-b |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/2] Add default binderfs devices
Binderfs was created to help provide private binder devices to containers in their own IPC namespace. Currently, every time a new binderfs instance is mounted, its private binder devices need to be created via IOCTL calls. This patch series eliminates the effort for creating the default binder devices for each binderfs instance by creating them automatically.
Hridya Valsaraju (2):
binder: Add default binder devices through binderfs when configured
binder: Validate the default binderfs device names.
drivers/android/binder.c | 5 +++-- drivers/android/binder_internal.h | 2 ++ drivers/android/binderfs.c | 35 ++++++++++++++++++++++++++++--- 3 files changed, 37 insertions(+), 5 deletions(-)
Signature · 1 line
2.22.0.770.g0f2c4a37fd-goog