From: "Daniel P. Berrange" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Move some trace events to the correct files
Date: Mon, 19 Sep 2016 10:57:09 +0100 [thread overview]
Message-ID: <20160919095709.GK15201@redhat.com> (raw)
In-Reply-To: <87zin4jjzm.fsf@dusky.pond.sub.org>
On Mon, Sep 19, 2016 at 11:51:09AM +0200, Markus Armbruster wrote:
> "Daniel P. Berrange" <berrange@redhat.com> writes:
>
> > When I split up the monolithic trace-events file, a few
> > events ended up in incorrect files, partly due to incorrect
> > file name annotations against the events, partly due to my
> > mistakes.
>
> Are you aware of scripts/cleanup-trace-events.pl?
No, I've not seen it before now.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-09-19 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 17:03 [Qemu-devel] [PATCH 0/4] Move some trace events to the correct files Daniel P. Berrange
2016-09-14 17:03 ` [Qemu-devel] [PATCH 1/4] trace: move util/buffer.c trace points into correct file Daniel P. Berrange
2016-09-14 17:03 ` [Qemu-devel] [PATCH 2/4] trace: move util/qemu-coroutine*.c " Daniel P. Berrange
2016-09-14 17:03 ` [Qemu-devel] [PATCH 3/4] trace: move hw/mem/pc-dimm.c " Daniel P. Berrange
2016-09-14 17:03 ` [Qemu-devel] [PATCH 4/4] trace: move hw/virtio/virtio-balloon.c " Daniel P. Berrange
2016-09-14 17:44 ` [Qemu-devel] [PATCH 0/4] Move some trace events to the correct files Eric Blake
2016-09-15 12:43 ` Stefan Hajnoczi
2016-09-19 9:51 ` Markus Armbruster
2016-09-19 9:57 ` Daniel P. Berrange [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=20160919095709.GK15201@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).