From: Anthony Liguori <aliguori@us.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/3] Tracing patches
Date: Mon, 02 Apr 2012 10:52:38 -0500 [thread overview]
Message-ID: <4F79CB46.4050800@us.ibm.com> (raw)
In-Reply-To: <1333105086-6047-1-git-send-email-stefanha@linux.vnet.ibm.com>
On 03/30/2012 05:58 AM, Stefan Hajnoczi wrote:
> The latest tracing fixes.
>
> Alon Levy (2):
> Makefile.target: code stp dependency on trace-events
> tracetool: dtrace: handle in and next reserved words
>
> Lee Essen (1):
> tracetool: dtrace disabled-events fix
Pulled. Thanks.
Regards,
Anthony Liguori
>
> Makefile.target | 2 +-
> scripts/tracetool | 22 ++++++++++++++++++----
> 2 files changed, 19 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2012-04-02 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 10:58 [Qemu-devel] [PULL 0/3] Tracing patches Stefan Hajnoczi
2012-03-30 10:58 ` [Qemu-devel] [PATCH 1/3] Makefile.target: code stp dependency on trace-events Stefan Hajnoczi
2012-03-30 10:58 ` [Qemu-devel] [PATCH 2/3] tracetool: dtrace disabled-events fix Stefan Hajnoczi
2012-03-30 10:58 ` [Qemu-devel] [PATCH 3/3] tracetool: dtrace: handle in and next reserved words Stefan Hajnoczi
2012-04-02 15:52 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-05 19:42 [Qemu-devel] [PULL 0/3] Tracing patches Stefan Hajnoczi
2016-09-06 12:32 ` Peter Maydell
2017-03-16 7:04 Stefan Hajnoczi
2017-03-16 15:31 ` Peter Maydell
2018-01-29 16:07 Stefan Hajnoczi
2018-01-29 16:14 ` no-reply
2018-01-30 11:58 ` Stefan Hajnoczi
2018-01-30 10:50 ` Peter Maydell
2018-02-19 16:19 Stefan Hajnoczi
2018-02-19 18:40 ` Peter Maydell
2019-09-18 13:21 Stefan Hajnoczi
2019-09-19 13:37 ` Peter Maydell
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=4F79CB46.4050800@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).