| commit | 8daf5ff7dddfec4d8435456a99aaf5e3c34a4437 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Jul 13 10:55:36 2023 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jan 17 13:30:40 2024 -0600 |
| tree | 0f6ac9b47085699e4e1b072395c7e65107756049 | |
| parent | a6130094057b61a205a8a9ca706db65f13ee1f8a [diff] |
cpu/pcie: remove deprecated association name There are currently no users of this association in the OpenBMC organization and the name chosen here does not match the association naming design. Remove these associations. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I811c0c49db71d89dab34567ddeaef3a5867ab3b1
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