qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trace: clean up trace-events files
Date: Thu, 26 Jan 2017 17:07:19 +0000	[thread overview]
Message-ID: <20170126170719.GA27101@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170125142022.GD15529@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

On Wed, Jan 25, 2017 at 02:20:22PM +0000, Daniel P. Berrange wrote:
> On Wed, Jan 25, 2017 at 02:14:26PM +0000, Stefan Hajnoczi wrote:
> > There are a number of unused trace events that
> > scripts/cleanup-trace-events.pl finds.  The "hw/vfio/pci-quirks.c"
> > filename was typoed and "qapi/qapi-visit-core.c" was missing the qapi/
> > directory prefix.
> > 
> > diff --git a/qapi/trace-events b/qapi/trace-events
> > index 2c5d3bc..82a0b73 100644
> > --- a/qapi/trace-events
> > +++ b/qapi/trace-events
> > @@ -1,4 +1,4 @@
> > -# qapi-visit-core.c
> > +# qapi/qapi-visit-core.c
> >  visit_free(void *v) "v=%p"
> >  visit_complete(void *v, void *opaque) "v=%p opaque=%p"
> >  
> > @@ -15,7 +15,6 @@ visit_end_alternate(void *v, void *obj) "v=%p obj=%p"
> >  
> >  visit_optional(void *v, const char *name, bool *present) "v=%p name=%s present=%p"
> >  
> > -visit_type_enum(void *v, const char *name, int *obj) "v=%p name=%s obj=%p"
> 
> The actual bug is that the source file is mistakenly not calling this
> trace point - we shouldn't delete it - we should call it from the
> visit_type_enum() method

I'll add a patch to the v2 series to fix this.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      reply	other threads:[~2017-01-26 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 14:14 [Qemu-devel] [PATCH] trace: clean up trace-events files Stefan Hajnoczi
2017-01-25 14:20 ` Daniel P. Berrange
2017-01-26 17:07   ` Stefan Hajnoczi [this message]

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=20170126170719.GA27101@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=berrange@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).