From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] [GIT PULL] tracing: cleanups
Date: Thu, 10 May 2012 10:57:23 +0200 [thread overview]
Message-ID: <20120510085723.GB8186@gmail.com> (raw)
In-Reply-To: <20120509165751.114716410@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> Please pull the latest tip/perf/core tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> tip/perf/core
>
> Head SHA1: 68179686ac67cb08f08b1ef28b860d5ed899f242
>
>
> Jiri Olsa (1):
> tracing: Use seq_*_private interface for some seq files
>
> Minho Ban (1):
> tracing: Prevent wasting time evaluating parameters in trace_preempt_on/off
>
> Steven Rostedt (1):
> tracing: Remove ftrace_disable/enable_cpu()
>
> ----
> include/linux/ftrace.h | 8 ++++--
> kernel/trace/ftrace.c | 44 +++++++---------------------
> kernel/trace/trace.c | 74 +++++-------------------------------------------
> 3 files changed, 24 insertions(+), 102 deletions(-)
Pulled, thanks Steve!
Ingo
prev parent reply other threads:[~2012-05-10 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 16:57 [PATCH 0/3] [GIT PULL] tracing: cleanups Steven Rostedt
2012-05-09 16:57 ` [PATCH 1/3] tracing: Prevent wasting time evaluating parameters in trace_preempt_on/off Steven Rostedt
2012-05-09 16:57 ` [PATCH 2/3] tracing: Use seq_*_private interface for some seq files Steven Rostedt
2012-05-09 16:57 ` [PATCH 3/3] tracing: Remove ftrace_disable/enable_cpu() Steven Rostedt
2012-05-09 17:43 ` [PATCH 0/3] [GIT PULL] tracing: cleanups Ingo Molnar
2012-05-10 8:57 ` Ingo Molnar [this message]
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=20120510085723.GB8186@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox