qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 3/6] qapi: rename prefix QEVENT to Q_EVENT


From: Eric Blake
Subject: Re: [Qemu-devel] [PATCH 3/6] qapi: rename prefix QEVENT to Q_EVENT
Date: Mon, 21 Oct 2013 21:41:33 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0

On 10/21/2013 03:16 AM, Wenchao Xia wrote:
> The define will be moved to qapi-schema.json later, so rename the
> prefix to match its naming style.

Wouldn't it be simpler to fix the code generator to special case QEvent
to turn into QEVENT, instead of having to go through this churn?  But if
we _like_ the Q_EVENT_ prefix, then this looks fairly mechanical:

> 
> Also fixed code style error reported in spice-core.c.
> 
> Signed-off-by: Wenchao Xia <address@hidden>
> ---
>  balloon.c                 |    2 +-
>  block.c                   |    4 +-
>  block/qcow2-refcount.c    |    2 +-
>  blockdev.c                |    4 +-
>  blockjob.c                |    5 ++-
>  cpus.c                    |    2 +-
>  hw/acpi/core.c            |    2 +-
>  hw/core/qdev.c            |    2 +-
>  hw/misc/pvpanic.c         |    2 +-
>  hw/net/virtio-net.c       |    2 +-
>  hw/watchdog/watchdog.c    |    2 +-
>  include/monitor/monitor.h |   58 +++++++++++++++++-----------------
>  monitor.c                 |   74 ++++++++++++++++++++++----------------------
>  target-s390x/kvm.c        |    2 +-
>  ui/spice-core.c           |    8 ++--
>  ui/vnc.c                  |    6 ++--
>  vl.c                      |   14 ++++----
>  17 files changed, 96 insertions(+), 95 deletions(-)

If no one else is as opposed to the Q_EVENT naming as I seem to be, then
you can add my reluctant

Reviewed-by: Eric Blake <address@hidden>

in that your change is mechanical and correct.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]