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>,
Pekka Paalanen <pq@iki.fi>
Subject: Re: [PATCH 0/3] ftrace: updates for tip
Date: Mon, 29 Dec 2008 12:46:31 +0100 [thread overview]
Message-ID: <20081229114631.GA22727@elte.hu> (raw)
In-Reply-To: <20081224042410.746044949@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> This series restructures the output functions of trace.c.
>
> Events are now registered and maintaining an event output is
> simplified by keeping the output close together.
>
> The following patches are in:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>
> branch: tip/devel
>
>
> Steven Rostedt (3):
> ftrace: remove obsolete print continue functionality
> ftrace: set up trace event hash infrastructure
> ftrace: change trace.c to use registered events
pulled, thanks Steve!
Ingo
next prev parent reply other threads:[~2008-12-29 11:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 4:24 [PATCH 0/3] ftrace: updates for tip Steven Rostedt
2008-12-24 4:24 ` [PATCH 1/3] ftrace: remove obsolete print continue functionality Steven Rostedt
2008-12-24 4:24 ` [PATCH 2/3] ftrace: set up trace event hash infrastructure Steven Rostedt
2008-12-24 4:24 ` [PATCH 3/3] ftrace: change trace.c to use registered events Steven Rostedt
2008-12-24 23:13 ` [PATCH 0/3] ftrace: updates for tip Frederic Weisbecker
2008-12-24 23:24 ` Frederic Weisbecker
2008-12-29 11:46 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 6:13 Steven Rostedt
2009-02-05 13:37 ` Ingo Molnar
2009-02-03 2:38 Steven Rostedt
2008-12-03 20:36 Steven Rostedt
2008-12-04 8:19 ` Ingo Molnar
2008-12-04 8:35 ` Ingo Molnar
2008-12-04 13:30 ` Steven Rostedt
2008-11-15 0:45 Steven Rostedt
2008-11-12 22:52 [PATCH 0/3] ftrace " Steven Rostedt
2008-11-13 8:50 ` 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=20081229114631.GA22727@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pq@iki.fi \
--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