Documentation of guest-get-vcpus and guest-get-memory-blocks has "This is a read-only operation". Similar commands don't. A "get" command that actually writes would be in surprisingly bad taste. Delete both instances of the sentence.
Signed-off-by: Markus Armbruster <[email protected]> Message-ID: <[email protected]> Reviewed-by: John Snow <[email protected]> [Straightforward conflict with commit 45a70e37ff (qapi: split intros for qga/qapi-schema.json) resolved] --- qga/qapi-schema.json | 4 ---- 1 file changed, 4 deletions(-) diff --git a/qga/qapi-schema.json b/qga/qapi-schema.json index 7b937713e6..a6cda5eae1 100644 --- a/qga/qapi-schema.json +++ b/qga/qapi-schema.json @@ -741,8 +741,6 @@ # @guest-get-vcpus: # Retrieve the list of the guest's logical processors. # -# This is a read-only operation. -# # Returns: The list of all VCPUs the guest knows about. Each VCPU is # put on the list exactly once, but their order is unspecified. # @@ -1100,8 +1098,6 @@ # @guest-get-memory-blocks: # Retrieve the list of the guest's memory blocks. # -# This is a read-only operation. -# # Returns: The list of all memory blocks the guest knows about. Each # memory block is put on the list exactly once, but their order is # unspecified. -- 2.55.0
