From: George Dunlap <george.dunlap@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Olaf Hering <olaf@aepfle.de>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v4 2/9] xenalyze: add to tools/xentrace/
Date: Tue, 2 Jun 2015 18:06:51 +0100 [thread overview]
Message-ID: <556DE2AB.3010504@eu.citrix.com> (raw)
In-Reply-To: <20150525083434.GS19083@zion.uk.xensource.com>
On 05/25/2015 09:34 AM, Wei Liu wrote:
> On Sat, May 23, 2015 at 08:24:11AM +0000, Olaf Hering wrote:
>> This merges xenalyze.hg, changeset 150:24308507be1d,
>> into tools/xentrace/xenalyze.c to have the tool and
>> public/trace.h in one place.
>>
>> Signed-off-by: Olaf Hering <olaf@aepfle.de>
>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
>> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> Cc: Ian Campbell <ian.campbell@citrix.com>
>> Cc: Wei Liu <wei.liu2@citrix.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
>
> George, are you happy with this change? I would like to get your ack /
> nack.
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
next prev parent reply other threads:[~2015-06-02 17:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 8:24 [PATCH v4 0/9] add xenalyze to staging Olaf Hering
2015-05-23 8:24 ` [PATCH v4 1/9] xentrace: install into sbin Olaf Hering
2015-05-25 8:33 ` Wei Liu
2015-06-02 17:03 ` George Dunlap
2015-05-23 8:24 ` [PATCH v4 2/9] xenalyze: add to tools/xentrace/ Olaf Hering
2015-05-25 8:34 ` Wei Liu
2015-06-02 17:06 ` George Dunlap [this message]
2015-05-23 8:24 ` [PATCH v4 3/9] xenalyze: increase NR_CPUS to 256 Olaf Hering
2015-05-23 8:24 ` [PATCH v4 4/9] xenalyze: print newline after unknown hvm events Olaf Hering
2015-05-23 8:24 ` [PATCH v4 5/9] xenalyze: include odd mmio states in default output Olaf Hering
2015-05-23 8:24 ` [PATCH v4 6/9] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-05-23 8:24 ` [PATCH v4 7/9] xenalyze: handle more events in sched_process Olaf Hering
2015-06-02 17:12 ` George Dunlap
2015-06-09 10:44 ` Olaf Hering
2015-05-23 8:24 ` [PATCH v4 8/9] xenalyze: remove traling whitespaces Olaf Hering
2015-05-23 8:24 ` [PATCH v4 9/9] xenalyze: remove argp_program_version Olaf Hering
2015-06-02 17:16 ` [PATCH v4 0/9] add xenalyze to staging George Dunlap
2015-06-03 10:33 ` Ian Campbell
2015-06-03 10:10 ` Ian Campbell
2015-06-03 10:15 ` Ian Campbell
2015-06-03 10:33 ` George Dunlap
2015-06-03 10:59 ` Ian Campbell
2015-06-03 11:16 ` George Dunlap
2015-06-03 11:21 ` George Dunlap
2015-06-03 11:34 ` Ian Campbell
2015-06-03 10:35 ` Julien Grall
2015-06-03 10:38 ` Andrew Cooper
2015-06-03 10:38 ` George Dunlap
2015-06-03 10:41 ` Andrew Cooper
2015-06-03 10:42 ` George Dunlap
2015-06-03 10:49 ` George Dunlap
2015-06-09 10:18 ` Olaf Hering
2015-06-09 11:31 ` Julien Grall
2015-06-09 11:38 ` George Dunlap
2015-06-09 23:21 ` Julien Grall
2015-06-15 9:23 ` George Dunlap
2015-06-15 12:44 ` Julien Grall
2015-06-15 13:46 ` George Dunlap
2015-06-16 7:21 ` Roger Pau Monné
2015-06-09 6:54 ` Olaf Hering
2015-06-09 11:07 ` Olaf Hering
2015-06-10 21:23 ` Julien Grall
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=556DE2AB.3010504@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.