Re: [Qemu-devel] [PATCH] qapi/misc.json: Remove superfluous words in CpuModelExpansionType

[Eric Blake]

On 10/3/18 5:46 AM, Kashyap Chamarthy wrote:
> While at it, s/QMU/QEMU in @CpuDefinitionInfo.

Could mention that it was a repetition of 'independent of'.

> Signed-off-by: Kashyap Chamarthy <address@hidden>
> ---
>   qapi/misc.json | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)

Reviewed-by: Eric Blake <address@hidden>

> diff --git a/qapi/misc.json b/qapi/misc.json
> index ada9af5add..f98de3a58c 100644
> --- a/qapi/misc.json
> +++ b/qapi/misc.json
> @@ -2017,7 +2017,7 @@
>   #
>   # @migration-safe: whether a CPU definition can be safely used for
>   #                  migration in combination with a QEMU compatibility machine
> -#                  when migrating between different QMU versions and between
> +#                  when migrating between different QEMU versions and between
>   #                  hosts with different sets of (hardware or software)
>   #                  capabilities. If not provided, information is not available
>   #                  and callers should not assume the CPU definition to be
> @@ -2126,11 +2126,11 @@
>   # @static: Expand to a static CPU model, a combination of a static base
>   #          model name and property delta changes. As the static base model 
> will
>   #          never change, the expanded CPU model will be the same, independent 
> of
> -#          independent of QEMU version, machine type, machine options, and
> -#          accelerator options. Therefore, the resulting model can be used by
> -#          tooling without having to specify a compatibility machine - e.g. 
> when
> -#          displaying the "host" model. static CPU models are migration-safe.
> -#
> +#          QEMU version, machine type, machine options, and accelerator 
> options.
> +#          Therefore, the resulting model can be used by tooling without having
> +#          to specify a compatibility machine - e.g. when displaying the "host"
> +#          model. The @static CPU models are migration-safe.
> +
>   # @full: Expand all properties. The produced model is not guaranteed to be
>   #        migration-safe, but allows tooling to get an insight and work with
>   #        model details.

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