diff options
| author | Eric Mosbarger <ericx.mosbarger@intel.com> | 2020-12-05 07:34:37 +0300 |
|---|---|---|
| committer | Eric Mosbarger <ericx.mosbarger@intel.com> | 2020-12-05 07:34:37 +0300 |
| commit | 9e6bca94a8d0f50e2628f53ba7589f6d3ae179ba (patch) | |
| tree | 68c4888e243d2329564ce9a6a5df00545369d33c | |
| parent | 27939937d95deb4ef627386482e044a0ba13356a (diff) | |
| download | openbmc-9e6bca94a8d0f50e2628f53ba7589f6d3ae179ba.tar.xz | |
Fake-change Wolf
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -31,7 +31,7 @@ general rule, this repository loosens the requirements of "form over function" and prefers to make some simplifying assumptions of BMC capabilities, chipsets, and required features. -### Can I upstream/release the code from this repository? +### Can I upstream/release code from this repository? It very much depends on the component. While in general the answer ends up being "yes", prior approval should be granted, as this repo contains future @@ -39,7 +39,7 @@ facing capabilities that may not have been announced yet. Please email OpenBMC.Support@intel.com to discuss. Appropriate licenses will be applied to the portions of this codebase that are approved for upstreaming. -### How to build for Wolf Pass +### How to build Wolf Pass ```bash export TEMPLATECONF=meta-openbmc-mods/meta-wolfpass/conf source oe-init-build-env |