From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/3] [GIT PULL] tracing: various fixes
Date: Tue, 17 Nov 2009 18:19:44 +0100 [thread overview]
Message-ID: <20091117171944.GA5967@elte.hu> (raw)
In-Reply-To: <20091117171242.761539651@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> This is based on top of tip/tracing/core.
>
> Please pull the latest tip/tracing/core-1 tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core-1
>
>
> Lai Jiangshan (1):
> tracing: Prevent build warning: 'ftrace_graph_buf' defined but not used
>
> Steven Rostedt (2):
> ring-buffer: Move access to commit_page up into function used
> tracing: Only print objcopy version warning once from recordmcount
>
> ----
> Makefile | 1 +
> kernel/trace/ftrace.c | 2 +-
> kernel/trace/ring_buffer.c | 9 +++------
> scripts/recordmcount.pl | 12 ++++++++++--
> 4 files changed, 15 insertions(+), 9 deletions(-)
Pulled into tip:tracing/core, thanks Steve!
Ingo
next prev parent reply other threads:[~2009-11-17 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 17:12 [PATCH 0/3] [GIT PULL] tracing: various fixes Steven Rostedt
2009-11-17 17:12 ` [PATCH 1/3] [PATCH 1/3] ring-buffer: Move access to commit_page up into function used Steven Rostedt
2009-11-17 17:12 ` [PATCH 2/3] [PATCH 2/3] tracing: Prevent build warning: ftrace_graph_buf defined but not used Steven Rostedt
2009-11-17 17:12 ` [PATCH 3/3] [PATCH 3/3] tracing: Only print objcopy version warning once from recordmcount Steven Rostedt
2009-11-17 17:19 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-06 23:04 [PATCH 0/3] [GIT PULL] tracing: various fixes Steven Rostedt
2010-05-07 6:34 ` Ingo Molnar
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=20091117171944.GA5967@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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