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
1 file changed
tree: 3897516aa4b50acf8dea7db79d58333f2a0f0a29
  1. architecture/
  2. designs/
  3. development/
  4. logo/
  5. release/
  6. security/
  7. style/
  8. testing/
  9. tof/
  10. userguide/
  11. anti-patterns.md
  12. cheatsheet.md
  13. code-of-conduct.md
  14. console.md
  15. CONTRIBUTING.md
  16. cpp-style-and-conventions.md
  17. features.md
  18. glossary.md
  19. host-management.md
  20. IPMITOOL-cheatsheet.md
  21. kernel-development.md
  22. LICENSE
  23. maintainer-workflow.md
  24. MAINTAINERS
  25. Makefile
  26. meta-layer-guidelines.md
  27. openbmc-conversion.md
  28. OWNERS
  29. README.md
  30. REDFISH-cheatsheet.md
  31. rest-api.md
  32. REST-cheatsheet.md
  33. SECURITY.md
  34. subtree.md
  35. yocto-development.md
README.md

OpenBMC documentation

The OpenBMC project is a Linux Foundation project whose goal is to produce a customizable, open-source firmware stack for Baseboard Management Controllers (BMCs). This repository contains documentation for OpenBMC as a whole. There may be component-specific documentation in the repository for each component.

The features document lists the project's major features with links to more information.

Contact

OpenBMC Development

These documents contain details on developing OpenBMC code itself

OpenBMC Usage

These documents describe how to use OpenBMC, including using the programmatic interfaces to an OpenBMC system.