summaryrefslogtreecommitdiff
path: root/meta-openembedded/meta-python/recipes-devtools/python/python3-crc32c_2.3.bb
diff options
context:
space:
mode:
authorEd Tanous <ed@tanous.net>2021-07-31 01:20:11 +0300
committerEd Tanous <ed@tanous.net>2022-12-12 23:03:53 +0300
commit7ba6171bf57405008aeea92acabedb2588d7da29 (patch)
treee3db5087ac05af7d9defb4a3c5b79793ac25d832 /meta-openembedded/meta-python/recipes-devtools/python/python3-crc32c_2.3.bb
parent502b40043e3dde083122dff8402979db6240a1c3 (diff)
downloadopenbmc-7ba6171bf57405008aeea92acabedb2588d7da29.tar.xz
Remove patches against OpenBMC projects
It's not clear why these patches were added in this manner, but they can't really remain here from a maintenance perspective. Pinning one platform on an old version of x86-power-control, as well as setting a specific patch means that it's impossible for people to test and use upstream code with it. It is also explicitly called out as item #1 on the meta layer guidelines for this reason: https://github.com/openbmc/docs/blob/master/meta-layer-guidelines.md To the maintainters of this meta layer, please work with Jason and Kwin (the x86-power-control maintainers) to get your features accounted for in the normal build, adding build flags and configuration entries where appropriate. Tested: This almost certainly breaks power control on ethanolx, but given the way this patch was merged, there's really no way to avoid that. Signed-off-by: Ed Tanous <ed@tanous.net> Change-Id: I1f6a40e5b01c36441ff8d66e8e73265e0e009a4f
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python3-crc32c_2.3.bb')
0 files changed, 0 insertions, 0 deletions