From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] Move some trace events to the correct files
Date: Wed, 14 Sep 2016 18:03:40 +0100 [thread overview]
Message-ID: <1473872624-23285-1-git-send-email-berrange@redhat.com> (raw)
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.
These patches were previously posted as part of my giant
series, but since they're trivial I figure they can be
usefully queued for merge while the rest of the giant
series is debated
https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg01714.html
Daniel P. Berrange (4):
trace: move util/buffer.c trace points into correct file
trace: move util/qemu-coroutine*.c trace points into correct file
trace: move hw/mem/pc-dimm.c trace points into correct file
trace: move hw/virtio/virtio-balloon.c trace points into correct file
Makefile.objs | 1 +
hw/i386/trace-events | 4 ----
hw/mem/trace-events | 5 +++++
hw/virtio/trace-events | 5 +++++
io/trace-events | 6 ------
trace-events | 17 -----------------
util/trace-events | 19 +++++++++++++++++++
7 files changed, 30 insertions(+), 27 deletions(-)
create mode 100644 hw/mem/trace-events
--
2.7.4
next reply other threads:[~2016-09-14 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 17:03 Daniel P. Berrange [this message]
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
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=1473872624-23285-1-git-send-email-berrange@redhat.com \
--to=berrange@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.