On Wed, Jan 11, 2017 at 6:09 PM, Andrew F. Davis afd@ti.com wrote:
Changes involving High-Security boards should be CC'd for additional assessment of the security implications.
Signed-off-by: Andrew F. Davis afd@ti.com
Recently some fastboot additions have been made that may effect security on our HS boards by letting some boot methods work around our chain-of- trust. It would be nice to get a CC for changes that directly effect these HS boards so I have a chance to check for this kind of thing.
MAINTAINERS | 11 +++++++++++ 1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS index 793ff49f68..1ea7ae013a 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -434,6 +434,17 @@ S: Maintained F: drivers/spmi/ F: include/spmi/
+TI SYSTEM SECURITY +M: Andrew F. Davis afd@ti.com +S: Supported +F: arch/arm/mach-omap2/omap5/sec_entry_cpu1.S +F: arch/arm/mach-omap2/omap5/sec-fxns.c +F: arch/arm/mach-omap2/sec-common.c +F: arch/arm/mach-omap2/config_secure.mk +F: configs/am43xx_hs_evm_defconfig +F: configs/am57xx_hs_evm_defconfig +F: configs/dra7xx_hs_evm_defconfig
I thought of commenting this but some how missed, configs/*_defconfig files shouldn't be part of MAINTAINERS it has a separate file in respective boards.
thanks!