public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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/7] git pull request for tip/tracing/ftace
Date: Wed, 11 Feb 2009 10:10:02 +0100	[thread overview]
Message-ID: <20090211091002.GH21105@elte.hu> (raw)
In-Reply-To: <20090210173504.973802731@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> Ingo,
> 
> The following is based off of tip/tracing/ftrace.
> 
> -- Steve
> 
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: tip/tracing/ftrace
> 
> 
> Lai Jiangshan (2):
>       ring_buffer: fix typing mistake
>       ring_buffer: fix ring_buffer_read_page()
> 
> Steven Rostedt (1):
>       tracing, x86: fix constraint for parent variable
> 
> Tobias Klauser (1):
>       tracing: storage class should be before const qualifier
> 
> Wenji Huang (3):
>       tracing: remove unneeded variable
>       tracing: provide correct return value after outputting the event
>       tracing: fix typos in comments
> 
> ----
>  arch/x86/kernel/ftrace.c             |    9 +++---
>  include/linux/ring_buffer.h          |    2 +-
>  kernel/trace/ring_buffer.c           |   46 +++++++++++++++++++--------------
>  kernel/trace/trace.c                 |    2 +-
>  kernel/trace/trace_branch.c          |    4 +--
>  kernel/trace/trace_functions_graph.c |   14 +++++-----
>  kernel/trace/trace_hw_branches.c     |    2 +-
>  kernel/trace/trace_sysprof.c         |    2 +-
>  8 files changed, 42 insertions(+), 39 deletions(-)

Pulled into tip:tracing/ftrace, thanks Steve!

Note, i cherry-picked this fix into tip:tracing/urgent:

  9666578: tracing, x86: fix constraint for parent variable

As in theory GCC can miscompile the function-return-tracer, right?

	Ingo

  parent reply	other threads:[~2009-02-11  9:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 17:35 [PATCH 0/7] git pull request for tip/tracing/ftace Steven Rostedt
2009-02-10 17:35 ` [PATCH 1/7] ring_buffer: fix typing mistake Steven Rostedt
2009-02-10 17:35 ` [PATCH 2/7] ring_buffer: fix ring_buffer_read_page() Steven Rostedt
2009-02-10 17:35 ` [PATCH 3/7] tracing, x86: fix constraint for parent variable Steven Rostedt
2009-02-10 17:35 ` [PATCH 4/7] tracing: storage class should be before const qualifier Steven Rostedt
2009-02-10 17:35 ` [PATCH 5/7] tracing: remove unneeded variable Steven Rostedt
2009-02-10 17:35 ` [PATCH 6/7] tracing: provide correct return value after outputting the event Steven Rostedt
2009-02-10 17:35 ` [PATCH 7/7] tracing: fix typos in comments Steven Rostedt
2009-02-11  9:10 ` Ingo Molnar [this message]
2009-02-11 14:31   ` [PATCH 0/7] git pull request for tip/tracing/ftace Steven Rostedt

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=20090211091002.GH21105@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