All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Olaf Hering <olaf@aepfle.de>,
	xen-devel@lists.xen.org,
	George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/7] xenalyze: add to tools/misc
Date: Mon, 27 Apr 2015 15:04:12 +0100	[thread overview]
Message-ID: <553E41DC.5010208@citrix.com> (raw)
In-Reply-To: <1430140936-31279-2-git-send-email-olaf@aepfle.de>

On 27/04/15 14:22, Olaf Hering wrote:
> This merges xenalyze.hg, changeset 150:24308507be1d into tools/misc
> to have the tool and public/trace.h in one place.

Would this not be better in tools/xentrace/xenalyze ?

David

  reply	other threads:[~2015-04-27 14:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 13:22 [PATCH 0/7] add xenalyze to staging Olaf Hering
2015-04-27 13:22 ` [PATCH 1/7] xenalyze: add to tools/misc Olaf Hering
2015-04-27 14:04   ` David Vrabel [this message]
2015-04-28  5:57     ` Olaf Hering
2015-05-06 13:35     ` George Dunlap
2015-04-28  3:21   ` Wei Liu
2015-04-27 13:22 ` [PATCH 2/7] xenalyze: print newline after unknown hvm events Olaf Hering
2015-04-27 13:22 ` [PATCH 3/7] xenalyze: include odd mmio states in default output Olaf Hering
2015-04-27 13:22 ` [PATCH 4/7] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-04-27 13:22 ` [PATCH 5/7] xenalyze: disable sched_switch_process Olaf Hering
2015-04-28  3:16   ` Wei Liu
2015-04-28  5:58     ` Olaf Hering
2015-05-02 16:51       ` Wei Liu
2015-05-04  5:52         ` Olaf Hering
2015-04-27 13:22 ` [PATCH 6/7] xenalyze: handle more events in sched_process Olaf Hering
2015-04-27 13:22 ` [PATCH 7/7] xenalyze: remove traling whitespaces Olaf Hering

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=553E41DC.5010208@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=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.