tree 3b0343b283b37d484e719512b4236f52b88b47ee
parent d5cea14bea968d361eea32efa51e26c43093504f
author Ed Tanous <edtanous@google.com> 1631213203 -0700
committer Ed Tanous <ed@tanous.net> 1631915982 +0000

Implement a test for patch compliance

Per our documentation, patches outside of a couple specific directories
aren't allowed.  This commit implements a build-time check to see if any
new patches have been added.  Functionally, because there's several meta
layers that have broken the rules already, it has to contain a check
against the various patches that already exist in the tree.  This list
doesn't constitute a grandfather-ing in of those patches, but recognizes
that we can't immediately back them out, and having the maintainers take
care of them will take time.

Of note, this patchset also ignores patches in any of the poky layers,
as we can't define their policies, and allows patches in meta-phosphor,
as a backdoor in case we need a trapdoor to this policy, and all the
maintainers agree to it.

This change was originally checked into openbmc-build-scripts, but was
moved to support more users, and keeping this list up to date.  All
comments on the latest review from
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-build-scripts/+/46064/2
have been addressed.

Change-Id: I1c3e062278b4856cbfda910bdbf122e4b7539f89
Signed-off-by: Ed Tanous <edtanous@google.com>