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/org/open_power/Logging/PEL/Entry.interface.yaml b/yaml/org/open_power/Logging/PEL/Entry.interface.yaml
index 8576943..ad2a9a3 100644
--- a/yaml/org/open_power/Logging/PEL/Entry.interface.yaml
+++ b/yaml/org/open_power/Logging/PEL/Entry.interface.yaml
@@ -9,10 +9,10 @@
remain hidden from the customer. This event log is visible to
development personnel only, e.g. hardware recovered error, etc. No
service action is required for this type of errors. In general, when
- this value is used, the Error Action Flags has the value of
- "Hidden Error". An event log with this value is used primarily for
- error thresholding design/code debug or as a record to indicate an
- error frequency or trend.
+ this value is used, the Error Action Flags has the value of "Hidden
+ Error". An event log with this value is used primarily for error
+ thresholding design/code debug or as a record to indicate an error
+ frequency or trend.
- name: Subsystem
type: string
description: >
@@ -23,5 +23,5 @@
type: boolean
default: false
description: >
- Notifies the PEL handler that the management system acknowledged a PEL.
- The management system can be any system monitoring the hardware.
+ Notifies the PEL handler that the management system acknowledged a
+ PEL. The management system can be any system monitoring the hardware.