We are about to introduce a new set of enums that will be used
by FirmwareMappingMemory and that don't overlap with the formats
that are supported for FirmwareMappingFlash, so we need to
disambiguate things.

Signed-off-by: Andrea Bolognani <[email protected]>
---
 docs/interop/firmware.json | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/interop/firmware.json b/docs/interop/firmware.json
index da0362a2c0..ef9b976a34 100644
--- a/docs/interop/firmware.json
+++ b/docs/interop/firmware.json
@@ -233,7 +233,7 @@
              'verbose-dynamic', 'verbose-static' ] }
 
 ##
-# @FirmwareFormat:
+# @FirmwareFlashFormat:
 #
 # Formats that are supported for firmware images.
 #
@@ -243,7 +243,7 @@
 #
 # Since: 3.0
 ##
-{ 'enum': 'FirmwareFormat',
+{ 'enum': 'FirmwareFlashFormat',
   'data': [ 'raw', 'qcow2' ] }
 
 ##
@@ -265,7 +265,7 @@
 ##
 { 'struct' : 'FirmwareFlashFile',
   'data'   : { 'filename' : 'str',
-               'format'   : 'FirmwareFormat' } }
+               'format'   : 'FirmwareFlashFormat' } }
 
 
 ##
-- 
2.52.0


Reply via email to