| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Change-Id: Ie70c59acedbb7be2f5b34a83c1d3d011f440ba05
|
| |
| |
| |
| |
| |
| |
| | |
Inclusion of the makefile is done by the build system to enforce
the wanted order
Change-Id: I86d7c6fb08b6bb1f6e0385e951a54827345aaf84
|
|
|
|
|
|
|
|
|
|
| |
Rather than having to maintain out of tree changes, it is often
easier to maintain a hiearchy of changes, starting with the vendors
common config file. From there, inheriting products can pick up a base
and start to add or remove certain bits from it, making use of the
BOARD_SEPOLICY_* functions documented in external/sepolicy/README.
Change-Id: I28a4aaf6c126535f0a88001582641b234a750015
|
|
|
|
|
| |
Change-Id: I6f3249ff6f84862a5a1efee9a50e440381d6866a
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|
Rather than having to maintain out of tree changes, it is often
easier to maintain a hiearchy of changes, starting with the vendors
common config file. From there, inheriting products can pick up a base
and start to add or remove certain bits from it, making use of the
BOARD_SEPOLICY_* functions documented in external/sepolicy/README.
Change-Id: I28a4aaf6c126535f0a88001582641b234a750015
|