| commit | a0c724d3d425032213dbd48247d93cc76d61a331 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Aug 16 15:21:54 2024 -0400 |
| committer | Zane Shelley <zshelle@us.ibm.com> | Thu Aug 29 17:51:17 2024 +0000 |
| tree | b69c1ba522020bcef970a5f2f82469be3bb2f0ee | |
| parent | 622cd4bef036f34a400dca8f7d870ddf42b1e257 [diff] |
clang-format: re-format for clang-18 clang-format-18 isn't compatible with the clang-format-17 output, so we need to reformat the code with the latest version. The way clang-18 handles lambda formatting also changed, so we have made changes to the organization default style format to better handle lambda formatting. See I5e08687e696dd240402a2780158664b7113def0e for updated style. See Iea0776aaa7edd483fa395e23de25ebf5a6288f71 for clang-18 enablement. Change-Id: I1d204ff0a167c43688f2217e9dee5504c71cd4f0 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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