commit a1347418307d31a94bd21f22897aa508df938dcf
author Patrick Williams <patrick@stwcx.xyz> Tue Dec 06 10:56:22 2022 -0600
committer Patrick Williams <patrick@stwcx.xyz> Tue Dec 06 11:11:59 2022 -0600
tree dfcb36f177db4f34b8b3f2be3ff718b3648ef755
parent 3c7b858a13aa5fde934d6d789c9a6027490f78dc

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

yaml/xyz/openbmc_project/Dump/NewDump.interface.yaml

diff --git a/yaml/xyz/openbmc_project/Dump/NewDump.interface.yaml b/yaml/xyz/openbmc_project/Dump/NewDump.interface.yaml
index 330f1c2..ed603fb 100644
--- a/yaml/xyz/openbmc_project/Dump/NewDump.interface.yaml
+++ b/yaml/xyz/openbmc_project/Dump/NewDump.interface.yaml
@@ -1,9 +1,9 @@
 description: >
-    Implement to notify the creation of new dump.
-    Use this interface when the dump is already created and ready
-    to be offloaded. This interface will add a new dump object with the
-    properties provided. The existing internal create interface should
-    be used when the data is collected and the dump needs to be packaged.
+    Implement to notify the creation of new dump. Use this interface when the
+    dump is already created and ready to be offloaded. This interface will add a
+    new dump object with the properties provided. The existing internal create
+    interface should be used when the data is collected and the dump needs to be
+    packaged.
 
     Any OpenBMC implementation must provide exactly one implementation of
     xyz.openbmc_project.Dump.NewDump on /xyz/openbmc_project/dump.
@@ -16,11 +16,11 @@
           - name: SourceDumpId
             type: uint32
             description: >
-                The dump id provided by the source of the dump.
-                There are dumps which get generated outside the BMC, like a
-                system dump which gets generated and stored in the host memory.
-                All dumps will have a  unique id  but when communicating
-                to the source of the dump the SourceDumpId will be used.
+                The dump id provided by the source of the dump. There are dumps
+                which get generated outside the BMC, like a system dump which
+                gets generated and stored in the host memory. All dumps will
+                have a  unique id  but when communicating to the source of the
+                dump the SourceDumpId will be used.
           - name: Size
             type: uint64
             description: >