All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-kernel@vger.kernel.org,
	"Abhishek Sagar" <sagar.abhishek@gmail.com>,
	"Steven Rostedt" <rostedt@rostedt.homelinux.com>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [PATCH] ftrace: fix crash due to tracing of __naked functions
Date: Mon, 16 Mar 2009 09:33:18 -0700	[thread overview]
Message-ID: <49BE7F4E.2030905@am.sony.com> (raw)
In-Reply-To: <20090315085712.GB2865@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> On Sat, Mar 14, 2009 at 06:44:44PM -0700, Tim Bird wrote:
>> Uwe Kleine-K�nig wrote:
>>> without this change a kernel having CONFIG_FUNCTION_TRACER=y doesn't
>>> boot on many maschines.  It would be great if this change would make it
>>> into .29.
>> I'd like to ACK this patch (not sure if my opinion matters).
> 
> You're far too late, the patch has already been committed and the request
> for Linus to pull it has been sent.

OK, great!  I just wanted to add my 2 cents, since I didn't
see any resolution on the mailing list.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================


      reply	other threads:[~2009-03-16 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  7:46 [PATCH] ftrace: fix crash due to tracing of __naked functions Uwe Kleine-König
2009-03-09 10:27 ` Matthias Kaehlcke
2009-03-09 20:38 ` Uwe Kleine-König
2009-03-15  1:44 ` Tim Bird
2009-03-15  6:34   ` Uwe Kleine-König
2009-03-15  8:57   ` Russell King - ARM Linux
2009-03-16 16:33     ` Tim Bird [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=49BE7F4E.2030905@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@elte.hu \
    --cc=rostedt@rostedt.homelinux.com \
    --cc=sagar.abhishek@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.