From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Steven Rostedt <rostedt@goodmis.org>,
Jens Axboe <jens.axboe@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH tip 1/1] trace: Call tracing_reset_online_cpus before tracer->init()
Date: Fri, 6 Feb 2009 01:03:33 +0100 [thread overview]
Message-ID: <20090206000333.GD16040@elte.hu> (raw)
In-Reply-To: <20090205231236.GC23999@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> On Thu, Feb 05, 2009 at 06:02:00PM -0200, Arnaldo Carvalho de Melo wrote:
> > Impact: cleanup
> >
> > To make it easy for ftrace plugin writers, as this was open coded in
> > the existing plugins
> >
> > Cc: Ingo Molnar <mingo@elte.hu>
> > Cc: Frédéric Weisbecker <fweisbec@gmail.com>
> > Cc: Jens Axboe <jens.axboe@oracle.com>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> > ---
> > block/blktrace.c | 2 --
> > kernel/trace/trace.c | 8 +++++++-
> > kernel/trace/trace.h | 1 +
> > kernel/trace/trace_branch.c | 1 -
> > kernel/trace/trace_functions.c | 17 +++--------------
> > kernel/trace/trace_functions_graph.c | 1 -
> > kernel/trace/trace_hw_branches.c | 1 -
> > kernel/trace/trace_nop.c | 1 -
> > kernel/trace/trace_sched_switch.c | 8 +-------
> > kernel/trace/trace_selftest.c | 18 +++++++++---------
> > kernel/trace/trace_sysprof.c | 14 ++++----------
> > 11 files changed, 25 insertions(+), 47 deletions(-)
> >
>
> Heh, I will have to manage an "arnaldo" topic in my local git tree
> if I want to stay synced :-)
>
> Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Applied to tip:tracing/ftrace, thanks guys!
Ingo
next prev parent reply other threads:[~2009-02-06 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 20:02 [PATCH tip 1/1] trace: Call tracing_reset_online_cpus before tracer->init() Arnaldo Carvalho de Melo
2009-02-05 23:12 ` Frederic Weisbecker
2009-02-06 0:03 ` Ingo Molnar [this message]
2009-02-06 1:55 ` Arnaldo Carvalho de Melo
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=20090206000333.GD16040@elte.hu \
--to=mingo@elte.hu \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.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