| commit | 998c7beda3100c37b8931e8e2fafe7d40311297a | [log] [tgz] |
|---|---|---|
| author | Johnathan Mantey <johnathanx.mantey@intel.com> | Tue Jun 07 09:24:36 2022 -0700 |
| committer | Johnathan Mantey <johnathanx.mantey@intel.com> | Tue Jun 07 11:03:24 2022 -0700 |
| tree | e829c2ad3fdcebf430abb1794a14e46edb605a64 | |
| parent | aa46bf4d8108450eae1a200bcd5d5a778970d014 [diff] |
Remove read-only flag from NTPServers The NTPServers API no longer permits static assignment of NTPServers. This is a result of adding the read-only flag to the NTPServers D-Bus element. The API needs to allow submitters to assign NTPServers. This entry needs to allow read/write operations. Tested: After removing the read-only flag a Restclient PATCH request to the NTPServers succeeds. Inspection of the systemd.network configuration file confirms the values are propagated to the phosphor-network receiver. Change-Id: Ia2944738fe2bb9c5312207b1df21d8be9ddc5af2 Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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