From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: fweisbec@gmail.com, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/latency: Fix header output for latency tracers
Date: Tue, 18 Oct 2011 13:44:28 -0400 [thread overview]
Message-ID: <1318959868.3712.3.camel@frodo> (raw)
In-Reply-To: <20111018165313.GA12695@jolsa.brq.redhat.com>
On Tue, 2011-10-18 at 18:53 +0200, Jiri Olsa wrote:
> hi,
> any feedback on this?
>
Ah, I must have missed this patch. Strange, as I had it highlighted.
Anyway, I'm currently on my way to Prague, I'll see if I get some time
when I'm there to look at it in more detail and perhaps get it ready for
3.2.
Thanks,
-- Steve
next prev parent reply other threads:[~2011-10-18 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 14:03 [PATCH] tracing/latency: Fix header output for latency tracers Jiri Olsa
2011-10-18 16:53 ` Jiri Olsa
2011-10-18 17:44 ` Steven Rostedt [this message]
2011-11-05 2:24 ` Steven Rostedt
2011-11-07 15:08 ` [PATCHv2] " Jiri Olsa
2011-11-18 23:14 ` [tip:perf/core] " tip-bot for Jiri Olsa
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=1318959868.3712.3.camel@frodo \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox