| commit | bed657a128eac2b6e56417ee6545bfd3d6bc10d8 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Tue Apr 26 08:32:08 2022 -0500 |
| committer | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Tue Oct 11 10:06:22 2022 -0500 |
| tree | 62f6af357cd872e8d5f3e9d135bb4fb21b0c6d3d | |
| parent | 11efbb3c856af9d760e2d27ff276090d7b3510d5 [diff] |
Dump: Create: Add Unavailable error Some types of dumps cannot be initiated when another dump is in progress, return Unavailable error when the dump cannot be created. Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: I5590181a7d6c31cd40dc1d673924b56a1a38f186
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