public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Jens Axboe" <jens.axboe@oracle.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH tip 1/1] trace: assign defaults at register_ftrace_event
Date: Thu, 5 Feb 2009 14:36:43 +0100	[thread overview]
Message-ID: <20090205133643.GA19907@elte.hu> (raw)
In-Reply-To: <20090204221639.GO3440@ghostprotocols.net>


* Arnaldo Carvalho de Melo <acme@redhat.com> wrote:

> Impact: simplification of tracers
> 
> As all tracers are doing this we might as well do it in
> register_ftrace_event and save one branch each time we call these
> callbacks.
> 
> 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        |   13 +++++--------
>  kernel/trace/trace_branch.c |    3 ---
>  kernel/trace/trace_output.c |   13 +++++++++++--
>  4 files changed, 16 insertions(+), 15 deletions(-)

Applied to tip/tracing/ftrace, thanks guys!

	Ingo

      parent reply	other threads:[~2009-02-05 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 22:16 [PATCH tip 1/1] trace: assign defaults at register_ftrace_event Arnaldo Carvalho de Melo
2009-02-04 23:41 ` Frederic Weisbecker
2009-02-05  1:22   ` Arnaldo Carvalho de Melo
2009-02-05  1:24     ` Ingo Molnar
2009-02-05  1:37       ` Arnaldo Carvalho de Melo
2009-02-05  1:41       ` Frederic Weisbecker
2009-02-05  1:55         ` Ingo Molnar
2009-02-05  2:05           ` Frederic Weisbecker
2009-02-05  1:44       ` Steven Rostedt
2009-02-05 13:36 ` 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=20090205133643.GA19907@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --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