| commit | ba620541d0db7e3433babbd97c0413a371e6fb4a | |
| author | Thomas Huth <thuth@redhat.com> | |
| Wed, 22 Jul 2020 04:40:25 +0000 (22 06:40 +0200) | ||
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | |
| Mon, 27 Jul 2020 23:03:55 +0000 (27 18:03 -0500) | ||
| tree | ba69a80c728b42994e2c28b27455df228ced8c14 | treesnapshot (tar.gz zip) |
| parent | 3aaebc0cce4a4963f331f45643e17266646411e6 | commitdiff |
qga/qapi-schema: Document -1 for invalid PCI address fields
The "guest-get-fsinfo" could also be used for non-PCI devices in the
future. And the code in GuestPCIAddress() in qga/commands-win32.c seems
to be using "-1" for fields that it can not determine already. Thus
let's properly document "-1" as value for invalid PCI address fields.
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
The "guest-get-fsinfo" could also be used for non-PCI devices in the
future. And the code in GuestPCIAddress() in qga/commands-win32.c seems
to be using "-1" for fields that it can not determine already. Thus
let's properly document "-1" as value for invalid PCI address fields.
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
| qga/qapi-schema.json | diffblobblamehistory |