| commit | fa8679667d27e37a54c2d85a1bfc1d0cf23eba51 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Fri Jun 07 19:24:35 2024 -0500 |
| committer | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Tue Jun 11 12:12:13 2024 -0500 |
| tree | cab81c306c37e5045a13d89b3be88f4ef7a8c03a | |
| parent | cdda63820c2e132bc7da119ebcd9ea9a259565cb [diff] |
Add response code to system dump entry Add new property in the system dump entry for storing the response code returned by the host after requesting a new non-disruptive system dump. Change-Id: Ie6d8204ee6d7574fece9c8fc530bf28b09e50e63 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.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