commit | 1c4b02ea682b62a74bc28986c574774755d6cdaf | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Nov 09 14:00:29 2020 -0600 |
committer | ben.tyner <ben.tyner@ibm.com> | Tue Nov 10 22:25:23 2020 +0000 |
tree | 6b7f32967f032034c4fbbf6d2f0cc4e0e1e49a98 | |
parent | 1b1915eff34af43e2c6cb5dffc5addbdd705a916 [diff] |
Attn: Code cleanup based on local CI build output Modified code based on recommendations from local CI build. Cleaned up some potential null pointer dereferencing code. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I17fb40b25ce37627627c5112a6be786e2bac7c1f
In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.
Aditional details TBD.
For a standard OpenBMC release build, you want something like:
meson -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson -Dtests=enabled <build_dir> ninja -C <build_dir> test