reformat with latest settings
Reformat with the latest settings from openbmc-build-scripts (and
copy latest config files where appropriate). Fix a few minor
markdownlint issues.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I55205817c29dc3f182a165ddf9cd5d4e07b90063
diff --git a/yaml/xyz/openbmc_project/Telemetry/Report.interface.yaml b/yaml/xyz/openbmc_project/Telemetry/Report.interface.yaml
index e074da6..552200d 100644
--- a/yaml/xyz/openbmc_project/Telemetry/Report.interface.yaml
+++ b/yaml/xyz/openbmc_project/Telemetry/Report.interface.yaml
@@ -19,16 +19,15 @@
- name: ReadingParameters
type: array[struct[array[struct[object_path,string]],enum[self.OperationType],string,enum[self.CollectionTimescope],uint64]]
description: >
- Collection of metric parameters. Single entry consists of:
- array of [sensor path, metadata] tuples, operation type, metric ID,
- collection timescope and collection duration. Sensor paths point to
- sensors providing readings. Metadata contains client information; in
- case of Redfish it shall be metric's URI. Operation type provides
- knowledge of action executed on readings. Metric ID contains name that
- can be mapped to metadata (like Redfish Metric ID). Collection
- timescope specifies type of time scope applied to specific metric.
- Collection duration stores timestamp related with timescope type in
- milliseconds.
+ Collection of metric parameters. Single entry consists of: array of
+ [sensor path, metadata] tuples, operation type, metric ID, collection
+ timescope and collection duration. Sensor paths point to sensors
+ providing readings. Metadata contains client information; in case of
+ Redfish it shall be metric's URI. Operation type provides knowledge of
+ action executed on readings. Metric ID contains name that can be
+ mapped to metadata (like Redfish Metric ID). Collection timescope
+ specifies type of time scope applied to specific metric. Collection
+ duration stores timestamp related with timescope type in milliseconds.
- name: Readings
type: struct[uint64,array[struct[string,string,double,uint64]]]
description: >
diff --git a/yaml/xyz/openbmc_project/Telemetry/ReportManager.interface.yaml b/yaml/xyz/openbmc_project/Telemetry/ReportManager.interface.yaml
index 6f596e2..78a1fd7 100644
--- a/yaml/xyz/openbmc_project/Telemetry/ReportManager.interface.yaml
+++ b/yaml/xyz/openbmc_project/Telemetry/ReportManager.interface.yaml
@@ -78,8 +78,8 @@
type: uint64
description: >
Minimal allowed time between readings property updates. It limits
- Interval property in xyz.openbmc_project.Telemetry.Report and
- interval parameter in AddReport method.
+ Interval property in xyz.openbmc_project.Telemetry.Report and interval
+ parameter in AddReport method.
flags:
- const
- name: SupportedOperationTypes
diff --git a/yaml/xyz/openbmc_project/Telemetry/Trigger.interface.yaml b/yaml/xyz/openbmc_project/Telemetry/Trigger.interface.yaml
index 747c349..5b6515f 100644
--- a/yaml/xyz/openbmc_project/Telemetry/Trigger.interface.yaml
+++ b/yaml/xyz/openbmc_project/Telemetry/Trigger.interface.yaml
@@ -30,9 +30,9 @@
type: array[dict[object_path,string]]
description: >
Map of sensors that is monitored within trigger. D-Bus sensor path is
- used as map's key. Its value is a metadata that is used
- to store user data about sensor. In Redfish, metadata will be set to
- endpoint corresponding to that sensor.
+ used as map's key. Its value is a metadata that is used to store user
+ data about sensor. In Redfish, metadata will be set to endpoint
+ corresponding to that sensor.
- name: Thresholds
type: variant[array[struct[enum[self.Type],uint64,enum[self.Direction],double]],array[struct[string,enum[self.Severity],uint64,string]]]
description: >