From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ftrace: re-enable dynamic ftrace for ARM
Date: Sun, 14 Feb 2010 01:24:44 +0530 [thread overview]
Message-ID: <20100213195444.GA31190@debian> (raw)
In-Reply-To: <20100201211101.GB26532@pengutronix.de>
On Mon, Feb 01, 2010 at 10:11:02PM +0100, Uwe Kleine-K?nig wrote:
> That's OK for me. Then the only thing that would be nice would be some
> more documentation. E.g. how looks the function prologue in the two
> cases, which of these instruction is patched?
>
> This doesn't need to be a stopper for your patch, it's on my long term
> todo list already to add some documentation to the (non-dynamic) ftrace
> on arm. I wouldn't mind to add the documentation myself, but not now.
I've add this documentation (among other things) in the updated patch
set I've just posted.
Rabin
prev parent reply other threads:[~2010-02-13 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 17:33 [PATCH 1/2] ftrace: pass KBUILD_CFLAGS along with CC to record_mcount.pl Rabin Vincent
2010-01-31 17:33 ` [PATCH 2/2] ftrace: re-enable dynamic ftrace for ARM Rabin Vincent
2010-02-01 10:28 ` Uwe Kleine-König
2010-02-01 16:53 ` Rabin Vincent
2010-02-01 21:11 ` Uwe Kleine-König
2010-02-13 19:54 ` Rabin Vincent [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=20100213195444.GA31190@debian \
--to=rabin@rab.in \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).