commit | dc5b0ff1d62ffbf232bde9753d1c071e2ff64069 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Jan 14 14:01:39 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Jan 14 21:06:31 2021 +0000 |
tree | f521b8772b168af88c849a349ffa5435bd02b774 | |
parent | fe2757b0883a17d87561ecfc44d5c3a692f1373d [diff] |
Attn: Code cleanup based on CI build suggestions Lessened the scope of some variables, made explicit a constructor, changed a variable name that was shadowing a function name, removed some unused code. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I430f6dece8b606318a0ffa476bf06f9a0060f72d
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