From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MAINTAINERS: Add maintainer for TI security related files
Date: Sun, 15 Jan 2017 13:53:58 -0500 [thread overview]
Message-ID: <20170115185358.GQ19689@bill-the-cat> (raw)
In-Reply-To: <CAD6G_RS9Jcgrc=ojsy91uj6TZjbgHnXtjSMioRLDyHvdAUbmkg@mail.gmail.com>
On Sun, Jan 15, 2017 at 07:50:35PM +0100, Jagan Teki wrote:
> 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.
I'm indifferent in cases like this. For example, dra7xx_hs_evm has two
maintainers, Andrew (due to the security side) and Lokesh (who owns the
TI ref platforms in general). Making Andrew edit 3 (4 with the
am335x_hs_evm_defconfig coming soon) MAINTAINERS files to add 4 lines
each won't add to the clarity of things as get_maintainer.pl should do
the correct thing and list both, today.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170115/f7195501/attachment.sig>
prev parent reply other threads:[~2017-01-15 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:09 [U-Boot] [PATCH] MAINTAINERS: Add maintainer for TI security related files Andrew F. Davis
2017-01-15 18:32 ` [U-Boot] " Tom Rini
2017-01-15 18:50 ` [U-Boot] [PATCH] " Jagan Teki
2017-01-15 18:53 ` Tom Rini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170115185358.GQ19689@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox