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: Fri, 7 May 2010 08:34:04 +0200 [thread overview]
Message-ID: <20100507063404.GC3870@elte.hu> (raw)
In-Reply-To: <20100506230459.278936703@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> Ingo,
>
> Please pull the latest tip/tracing/core tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core
>
>
> Li Zefan (1):
> tracing: Make the documentation clear on trace_event boot option
>
> Steven Rostedt (1):
> tracing: Fix tracepoint.h DECLARE_TRACE() to allow more than one header
>
> Thiago Farina (1):
> tracing: Fix "integer as NULL pointer" warning.
>
> ----
> Documentation/trace/events.txt | 3 +-
> include/linux/tracepoint.h | 114 +++++++++++++++++++++-------------------
> include/trace/define_trace.h | 5 ++
> include/trace/events/napi.h | 10 +++-
> kernel/trace/trace_output.c | 2 +-
> 5 files changed, 75 insertions(+), 59 deletions(-)
Pulled, thanks Steve!
Ingo
next prev parent reply other threads:[~2010-05-07 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 23:04 [PATCH 0/3] [GIT PULL] tracing: various fixes Steven Rostedt
2010-05-06 23:05 ` [PATCH 1/3] tracing: Make the documentation clear on trace_event boot option Steven Rostedt
2010-05-06 23:05 ` [PATCH 2/3] tracing: Fix tracepoint.h DECLARE_TRACE() to allow more than one header Steven Rostedt
2010-05-06 23:05 ` [PATCH 3/3] tracing: Fix "integer as NULL pointer" warning Steven Rostedt
2010-05-07 6:34 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-17 17:12 [PATCH 0/3] [GIT PULL] tracing: various fixes Steven Rostedt
2009-11-17 17:19 ` 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=20100507063404.GC3870@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