Require patches follow yocto upstreaming rules
For meta layer patches, Yocto has a well-formed process for handling
patches. While patches should ideally be avoided, for the patches we do
choose to maintain, we should follow the best practices that yocto
defines to make sure they're maintainable.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ie75bf81bc31381a7eb036f4cbafd10b17fda8f19
diff --git a/meta-layer-guidelines.md b/meta-layer-guidelines.md
index b04b7ae..25e5487 100644
--- a/meta-layer-guidelines.md
+++ b/meta-layer-guidelines.md
@@ -47,7 +47,10 @@
Submit any changes needed to the Yocto upstream repositories, using their
process. If the Yocto process has gone several weeks without responses,
cherry-pick the commit into the OpenBMC tree, with a pointer to the review in
-the commit message.
+the commit message, and documentation. The patch commit message should follow
+the Yocto requirements for patch comments, including a statement of the patch
+upstream status.
+[yocto patch requirements](https://wiki.yoctoproject.org/wiki/Best_Known_Methods_%28BKMs%29_for_Package_Updating#Patch_Comments)
## Meta layers should avoid using EXTRA_OEMAKE and EXTRA_OEMESON