| commit | c49aa1b0e971a0308f320c98b05074e3a6c9d4f8 | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Mon Jan 27 19:38:02 2025 -0800 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Tue Jan 28 10:58:53 2025 -0800 |
| tree | 19fd59c91471b5f0c3763655f78a57c9d5419fe0 | |
| parent | c7560faae59f3c51404829d6f410b58034d602b8 [diff] |
add the redfish mapping for leak detector events DTMF has released the Redfish Message Registry [1] with Leak events, so update the related redfish mapping for Leak Detector events. Also drop the en section as this will come from standard redfish definitions. References: [1] https://www.dmtf.org/sites/default/files/standards/documents/DSP2065_2024.4.pdf Change-Id: I8be7314ba7c21da6a576668e1e29dbb3d7b7913c Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
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 and org/freedesktop 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