Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / 257c17da484244ae81b98d4bb12a052187d2c57e
commit257c17da484244ae81b98d4bb12a052187d2c57e[log] [tgz]
authorJonathan Doman <jonathan.doman@intel.com>Fri Feb 12 15:27:19 2021 -0800
committerJonathan Doman <jonathan.doman@intel.com>Fri Feb 12 16:38:39 2021 -0800
treefd770efe7d945fec044ffaea290f4ae77c1a871f
parentb2bbac7e2986decf1ed5d102e79f1872ddd84881 [diff]
Reduce Common.Device error messages

The full yaml error description is sent with the error reply message
across D-Bus. These two error messages are unnecessarily verbose for
that purpose, so move most of it into a yaml comment.

Tested:
Used busctl to call method that replied with WriteFailure and confirmed
the error message was reduced.

Signed-off-by: Jonathan Doman <jonathan.doman@intel.com>
Change-Id: Icebf2079a18214435e59d05d0ba39eb05b2094f0
1 file changed
tree: fd770efe7d945fec044ffaea290f4ae77c1a871f
  1. com/
  2. gen/
  3. org/
  4. subprojects/
  5. xyz/
  6. .gitignore
  7. LICENSE
  8. MAINTAINERS
  9. meson.build
  10. meson_options.txt
  11. README.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Building

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.

Configuration

Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References