Re: [PATCH v3 03/34] docs/devel/qapi-code-gen: Clarify allow-oob introspection

[Eric Blake]

On 3/15/20 9:46 AM, Markus Armbruster wrote:
> Mention SchemaInfo variant member "allow-oob" defaults to false.
>
> Signed-off-by: Markus Armbruster <address@hidden>
> ---
>   docs/devel/qapi-code-gen.txt | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)

Reviewed-by: Eric Blake <address@hidden>

> diff --git a/docs/devel/qapi-code-gen.txt b/docs/devel/qapi-code-gen.txt
> index 59d6973e1e..5906602504 100644
> --- a/docs/devel/qapi-code-gen.txt
> +++ b/docs/devel/qapi-code-gen.txt
> @@ -988,9 +988,9 @@ The SchemaInfo for a command has meta-type "command", and 
> variant
>   members "arg-type", "ret-type" and "allow-oob".  On the wire, the
>   "arguments" member of a client's "execute" command must conform to the
>   object type named by "arg-type".  The "return" member that the server
> -passes in a success response conforms to the type named by
> -"ret-type".  When "allow-oob" is set, it means the command supports
> -out-of-band execution.
> +passes in a success response conforms to the type named by "ret-type".
> +When "allow-oob" is true, it means the command supports out-of-band
> +execution.  It defaults to false.
>   
>   If the command takes no arguments, "arg-type" names an object type
>   without members.  Likewise, if the command returns nothing, "ret-type"

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org