Hi Kyösti >The commit hash you push to board-status with has to be one from >upstream, local changes are not really useful or acceptable. The >entire purpose is to have a known-good reference where board has >somewhat booted. You can go to parent of the commit above.
Yes, I have to do a commit for the local changes to make the board_status script happy. >Regarding the conflicting commit, it was there to be reviewed from Jan >24th and finally approved Sep 11th, having seen testing only on >pcengines/apu2 which is a different SoC. The other error is likely a >regression after two weeks of not being build-tested. Sounds like two >commits you need tol land first. So, before I can send the board status, should I wait for someone to upload the changes to the repository? Regards, Jorge Kyösti _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
