From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Neuling <mikey@neuling.org>
Subject: Re: [PATCH 0/2] ftrace: updates for powerpc
Date: Fri, 06 Feb 2009 18:04:19 +1100 [thread overview]
Message-ID: <1233903859.4612.119.camel@pasglop> (raw)
In-Reply-To: <20090206060328.181057235@goodmis.org>
On Fri, 2009-02-06 at 01:03 -0500, Steven Rostedt wrote:
> Paul,
>
> The first patch is a ftrace clean up to use the proper pr_debug macro.
>
> The second patch is to fix a compile error when dynamic ftrace
> is compiled in, but modules are not.
Did you find out the problem with the large USB module ?
Cheers,
Ben.
> The following patches are in:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>
> branch: ppc/ftrace
>
>
> Steven Rostedt (2):
> ftrace, powerpc: replace debug macro with proper pr_deug
> powerpc, ftrace: fix compile error when modules not configured
>
> ----
> arch/powerpc/kernel/ftrace.c | 42 +++++++++++++++++++++++++-----------------
> 1 files changed, 25 insertions(+), 17 deletions(-)
next prev parent reply other threads:[~2009-02-06 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 6:03 [PATCH 0/2] ftrace: updates for powerpc Steven Rostedt
2009-02-06 6:03 ` [PATCH 1/2] ftrace, powerpc: replace debug macro with proper pr_deug Steven Rostedt
2009-02-06 6:07 ` Steven Rostedt
2009-02-06 7:05 ` Benjamin Herrenschmidt
2009-02-06 13:29 ` Steven Rostedt
2009-02-06 6:03 ` [PATCH 2/2] powerpc, ftrace: fix compile error when modules not configured Steven Rostedt
2009-02-06 6:07 ` Steven Rostedt
2009-02-06 6:23 ` Michael Neuling
2009-02-06 7:04 ` Benjamin Herrenschmidt [this message]
2009-02-06 13:28 ` [PATCH 0/2] ftrace: updates for powerpc Steven Rostedt
2010-05-10 10:27 ` hrtimer: about hres_active Iram Shahzad
2010-05-10 15:12 ` Thomas Gleixner
2010-05-11 1:39 ` Iram Shahzad
2010-05-11 8:33 ` Thomas Gleixner
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=1233903859.4612.119.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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