From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Subject: Re: [GIT PULL] tracing updates for 2.6.32
Date: Sat, 18 Jul 2009 10:57:43 +0200 [thread overview]
Message-ID: <20090718085743.GD7479@elte.hu> (raw)
In-Reply-To: <1247901421-6389-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Hi Ingo, Thomas,
>
> Here are some fixes and enhancements for the 2.6.32 tracing tree.
>
> Impacts:
>
> - A spurious warning in the lockless ring buffer had been shutdown
> - Simplifications of various ftrace code areas resulting in more deletions than
> additions.
>
> These changes have been based against tip:tracing/core
>
> Thanks,
>
> Frederic.
>
>
> The following changes since commit e202687927c132b1e1ff36b526b5e78ac33de840:
> Ingo Molnar (1):
> Merge branch 'tip/tracing/ring-buffer-3' of git://git.kernel.org/.../rostedt/linux-2.6-trace into tracing/core
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git tracing/core
>
> Lai Jiangshan (1):
> ring_buffer: Fix warning while ignoring cmpxchg return value
>
> Xiao Guangrong (3):
> tracing/function: Simplify __ftrace_replace_code()
> tracing/trace_stack: Cleanup for trace_lookup_stack()
> tracing/function: Cleanup for function tracer
>
> kernel/trace/ftrace.c | 89 +++++++++------------------------------
> kernel/trace/ring_buffer.c | 9 +++-
> kernel/trace/trace_functions.c | 4 +-
> kernel/trace/trace_stack.c | 9 +----
> 4 files changed, 30 insertions(+), 81 deletions(-)
Pulled, thanks a lot Frederic!
Ingo
prev parent reply other threads:[~2009-07-18 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 7:16 [GIT PULL] tracing updates for 2.6.32 Frederic Weisbecker
2009-07-18 7:16 ` [PATCH 1/4] ring_buffer: Fix warning while ignoring cmpxchg return value Frederic Weisbecker
2009-07-18 7:16 ` [PATCH 2/4] tracing/function: Simplify __ftrace_replace_code() Frederic Weisbecker
2009-07-18 7:17 ` [PATCH 3/4] tracing/trace_stack: Cleanup for trace_lookup_stack() Frederic Weisbecker
2009-07-18 7:17 ` [PATCH 4/4] tracing/function: Cleanup for function tracer Frederic Weisbecker
2009-07-18 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=20090718085743.GD7479@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=xiaoguangrong@cn.fujitsu.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 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.