| commit | 6e9b38a9e3e7154b0d5547395fb20dbd1bb9beee | [log] [tgz] |
|---|---|---|
| author | Arya K Padman <aryakpadman@gmail.com> | Mon Aug 26 03:45:25 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Sep 11 14:03:29 2024 +0000 |
| tree | d5279787de9586f7734ca231ca0673e2b08e6dc2 | |
| parent | 4028755da38ccccc09be2a15a0b482fa9d8dab7c [diff] |
Logging: Entry: Add errors to Resolved Property Add the error 'xyz.openbmc_project.Common.Error.Unavailable' to the 'Resolved' property of the Entry interface. This change helps in notifying the users when the attempt to set the Resolved property is prevented until the corresponding error log is addressed. For example, if the error log is associated with a HardwareIsolation entry (which indicates the faulty hardware) and has not been resolved yet; in this case, we need to prevent setting the 'Resolved' flag. Change-Id: I64da52e572ba33f888d33039ac604c57b86d84de Signed-off-by: Arya K Padman <aryakpadman@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