qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 0/3] Rename of the QObject visitors rearranged
Date: Tue, 25 Oct 2016 17:49:14 +0200	[thread overview]
Message-ID: <20161025154914.GA17307@redhat.com> (raw)
In-Reply-To: <1477406107-10757-1-git-send-email-armbru@redhat.com>

On Tue, Oct 25, 2016 at 04:35:04PM +0200, Markus Armbruster wrote:
> This is how I propose to rearrange PATCH 04+05 of Dan's "[PATCH v14
> 00/21] QAPI/QOM work for non-scalar object properties" (really v15) in
> my pull request, to make git's rename detection work.  The result is
> identical except for two comments I touched up:
> 
>   diff --git a/include/qapi/qobject-output-visitor.h b/include/qapi/qobject-output-visitor.h
>   index 358c959..8241877 100644
>   --- a/include/qapi/qobject-output-visitor.h
>   +++ b/include/qapi/qobject-output-visitor.h
>   @@ -20,7 +20,7 @@
>    typedef struct QObjectOutputVisitor QObjectOutputVisitor;
> 
>    /*
>   - * Create a new QOBJECT output visitor.
>   + * Create a new QObject output visitor.
>     *
>     * If everything else succeeds, pass @result to visit_complete() to
>     * collect the result of the visit.
>   diff --git a/qapi/qobject-output-visitor.c b/qapi/qobject-output-visitor.c
>   index df43cb8..8711270 100644
>   --- a/qapi/qobject-output-visitor.c
>   +++ b/qapi/qobject-output-visitor.c
>   @@ -150,7 +150,7 @@ static void qobject_output_type_int64(Visitor *v, const char *name,
>    static void qobject_output_type_uint64(Visitor *v, const char *name,
> 					  uint64_t *obj, Error **errp)
>    {
>   -    /* FIXME: QOBJECT outputs values larger than INT64_MAX as negative */
>   +    /* FIXME values larger than INT64_MAX become negative */
>        QObjectOutputVisitor *qov = to_qov(v);
>        qobject_output_add(qov, name, qint_from_int(*obj));
>    }

Looks fine to me.


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

  parent reply	other threads:[~2016-10-25 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 14:35 [Qemu-devel] [PATCH RFC 0/3] Rename of the QObject visitors rearranged Markus Armbruster
2016-10-25 14:35 ` [Qemu-devel] [PATCH RFC 1/3] qapi: rename *qmp-*-visitor* to *qobject-*-visitor* Markus Armbruster
2016-10-25 14:35 ` [Qemu-devel] [PATCH RFC 2/3] qapi: rename QmpInputVisitor to QObjectInputVisitor Markus Armbruster
2016-10-25 14:35 ` [Qemu-devel] [PATCH RFC 3/3] qapi: rename QmpOutputVisitor to QObjectOutputVisitor Markus Armbruster
2016-10-25 15:49 ` Daniel P. Berrange [this message]
2016-10-25 16:08 ` [Qemu-devel] [PATCH RFC 0/3] Rename of the QObject visitors rearranged Eric Blake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161025154914.GA17307@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).