John Snow <[email protected]> writes: > All conversions in this patch do not create a new documentation > insertion point, except for one at the very end. > > Signed-off-by: John Snow <[email protected]> > --- > docs/interop/firmware.json | 76 ++++++++++++++++---------------------- > 1 file changed, 31 insertions(+), 45 deletions(-) > > diff --git a/docs/interop/firmware.json b/docs/interop/firmware.json > index 421bee0e5ed..1efd32c6315 100644 > --- a/docs/interop/firmware.json > +++ b/docs/interop/firmware.json
[...] > @@ -250,12 +244,11 @@ > > ## > # @FirmwareFlashFile: > -# > -# Defines common properties that are necessary for loading a firmware > -# file into a pflash chip. The corresponding QEMU command line option > -# is "-drive file=@filename,format=@format". Note however that the > -# option-argument shown here is incomplete; it is completed under > -# @FirmwareMappingFlash. > +# Defines common properties that are necessary for loading a > +# firmware file into a pflash chip. The corresponding QEMU > +# command line option is "-drive file=@filename,format=@format". > +# Note however that the option-argument shown here is incomplete; > +# it is completed under @FirmwareMappingFlash. > # > # @filename: Specifies the filename on the host filesystem where the > # firmware file can be found. This smells like it could use a split, but it doesn't really matter; let's move on. [...] > @@ -467,9 +454,8 @@ > > ## > # @Firmware: > -# > -# Describes a firmware (or a firmware use case) to management > -# software. > +# Describes a firmware (or a firmware use case) to management > +# software. > # > # It is possible for multiple @Firmware elements to match the search > # criteria of management software. Applications thus need rules to This is the split you mentioned in the commit message. Correct?
