From: David Ahern <daahern@cisco.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Steven Rostedt <rostedt@goodmis.org>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, peterz@infradead.org, fweisbec@gmail.com,
paulus@samba.org, tglx@linutronix.de
Subject: Re: [PATCH 3/6] perf script: move printing of 'common' data from print_event and rename
Date: Thu, 10 Mar 2011 09:45:44 -0700 [thread overview]
Message-ID: <4D790038.502@cisco.com> (raw)
In-Reply-To: <20110310162038.GC23555@ghostprotocols.net>
On 03/10/11 09:20, Arnaldo Carvalho de Melo wrote:
>>> I think the merge with the libraries you mention is something that is
>>> not a precondition to merging David's work.
>>>
>>> And his work is at least moving things in the trace parts of tools/,
>>> that was so far dormant.
>>
>> Note, I'm not saying that his work should be put on hold. I actually
>> want to start it up again. Maybe I worded this response wrong. It was
>> more about bringing David up to speed on what I want to do next than
>> saying not to do this work.
>
> Right, I just wanted to make sure he doesn't spill his coffee with what
> could seem like yet another requirement to work on infrastructure to get
> his legitimate feature implementation merged :-)
I appreciate the clarification. Luckily, no coffee in hand.
I need to get the time-of-day strings done next, and someone else is
pushing the reverse callchain display (another local change I wanted to
get upstream). I could take a look at other requests - like common code
- as time allows.
David
>
> - Arnaldo
next prev parent reply other threads:[~2011-03-10 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 5:23 [PATCH 0/6 v4] perf script: add support for dumping events other than trace David Ahern
2011-03-10 5:23 ` [PATCH 1/6] perf script: change process_event prototype David Ahern
2011-03-16 13:53 ` [tip:perf/urgent] perf script: Change " tip-bot for David Ahern
2011-03-10 5:23 ` [PATCH 2/6] perf: remove print_graph_cpu and print_graph_proc from trace-event-parse David Ahern
2011-03-16 13:54 ` [tip:perf/urgent] perf tracing: Remove " tip-bot for David Ahern
2011-03-10 5:23 ` [PATCH 3/6] perf script: move printing of 'common' data from print_event and rename David Ahern
2011-03-10 15:20 ` Steven Rostedt
2011-03-10 15:51 ` Arnaldo Carvalho de Melo
2011-03-10 16:05 ` Steven Rostedt
2011-03-10 16:20 ` Arnaldo Carvalho de Melo
2011-03-10 16:45 ` David Ahern [this message]
2011-03-10 17:07 ` Steven Rostedt
2011-03-11 0:28 ` Frederic Weisbecker
2011-03-16 13:54 ` [tip:perf/urgent] perf script: Move " tip-bot for David Ahern
2011-03-10 5:23 ` [PATCH 4/6] perf script: support custom field selection for output David Ahern
2011-03-16 13:54 ` [tip:perf/urgent] perf script: Support " tip-bot for David Ahern
2011-03-10 5:23 ` [PATCH 5/6] perf script: add support for dumping symbols David Ahern
2011-03-16 13:55 ` [tip:perf/urgent] perf script: Add " tip-bot for David Ahern
2011-03-10 5:23 ` [PATCH 6/6] perf script: add support for H/W and S/W events David Ahern
2011-03-16 13:55 ` [tip:perf/urgent] perf script: Add " tip-bot for David Ahern
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=4D790038.502@cisco.com \
--to=daahern@cisco.com \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.