| commit | 6be85da9193d5c529b49fbf9345507e0be2b9477 | [log] [tgz] |
|---|---|---|
| author | Lei YU <yulei.sh@bytedance.com> | Tue Dec 01 20:03:46 2020 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 14 14:48:56 2020 +0000 |
| tree | 5ad1c89249fcb791480b4f88dcec2311fc0e0251 | |
| parent | 2bcb4b4f008ea70645ef6d755cc5967bd2bccfae [diff] |
Add SEL error yaml
The SEL error yaml is intented to be used to create logging entries with
specific metadata that will be consumed to present the IPMI SEL entries.
Tested: Verify the error could be created as entry with expected
metadata in logging.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Ia78b621e1b56563dd41114a779d531f5867076f8
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir