Changes involving High-Security boards should be CC'd for additional
assessment of the security implications.

Signed-off-by: Andrew F. Davis <a...@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 <a...@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
+
 TQ GROUP
 #M:    Martin Krause <martin.kra...@tq-systems.de>
 S:     Orphaned (Since 2016-02)
-- 
2.11.0

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to