| commit | 980fb7b56960951d8bfb471e9fe63b9d0bacf127 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Thu Feb 10 00:08:39 2022 -0600 |
| committer | Dhruvaraj S <dhruvaraj@gmail.com> | Wed May 08 15:22:50 2024 +0000 |
| tree | 49a5df49c744f5420537b96fe3c92343d220d715 | |
| parent | 61ade7b12d539d56ed19c49023bb9525cdc218b9 [diff] |
com-ibm-dump: Add response code to resource dump entry Add new property in the resource dump entry for storing the response code returned by the host after requesting a new resource dump. Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: I55a4de4e2b77c0387fba7412c122c28e9acdde7b
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