mirror of https://lore.kernel.org/lkml/
 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>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] [GIT PULL][v3.0] ftrace: urgent fixes
Date: Wed, 20 Jul 2011 16:43:56 +0200	[thread overview]
Message-ID: <20110720144354.GA25681@elte.hu> (raw)
In-Reply-To: <20110715033855.206223173@goodmis.org>


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

> Ingo,
> 
> I noticed that tip/perf/urgent wasn't pulled yet. I added it to this
> pull request. The first patch is what you reported to me, the second
> is a regression that Thomas stumbled upon.
> 
> Please pull the latest tip/perf/urgent-2 tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/perf/urgent-2
> 
> Head SHA1: f7bc8b61f65726ff98f52e286b28e294499d7a08
> 
> 
> Steven Rostedt (2):
>       ftrace: Fix warning when CONFIG_FUNCTION_TRACER is not defined
>       ftrace: Fix regression where ftrace breaks when modules are loaded
> 
> ----
>  include/linux/ftrace.h |    4 ++--
>  kernel/trace/ftrace.c  |   30 ++++++++++++++++++++++++++++--
>  2 files changed, 30 insertions(+), 4 deletions(-)

Pulled, thanks a lot Steve!

	Ingo

      parent reply	other threads:[~2011-07-20 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  3:38 Steven Rostedt
2011-07-15  3:38 ` [PATCH 1/2] ftrace: Fix warning when CONFIG_FUNCTION_TRACER is not defined Steven Rostedt
2011-07-15  3:38 ` [PATCH 2/2] ftrace: Fix regression where ftrace breaks when modules are loaded Steven Rostedt
2011-07-20 14:43 ` 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=20110720144354.GA25681@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome