From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64:ftrace: fix ftrace_modify_graph_caller for branch replace
Date: Thu, 12 Feb 2015 22:51:25 +0300 [thread overview]
Message-ID: <54DD043D.8000801@cogentembedded.com> (raw)
In-Reply-To: <b86ab19fb587cc7acc94a9b990afe0c33a073170.1423755113.git.panand@redhat.com>
Hello.
On 02/12/2015 06:33 PM, Pratyush Anand wrote:
> ftrace_enable_ftrace_graph_caller and ftrace_disable_ftrace_graph_caller
> should replace B(jmp) instruction and not BL(call) instruction.
> patch 9f1ae7596aad71d18c3e88a3927f3f76b037b8fe did a typo and used
s/patch/commit/. And please specify that commit's summary line in parens.
> AARCH64_INSN_BRANCH_LINK instead of AARCH64_INSN_BRANCH_NOLINK.
> Signed-off-by: Pratyush Anand <panand@redhat.com>
[...]
WBR, Sergei
next prev parent reply other threads:[~2015-02-12 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 15:33 [PATCH] ARM64:ftrace: fix ftrace_modify_graph_caller for branch replace Pratyush Anand
2015-02-12 19:51 ` Sergei Shtylyov [this message]
2015-02-13 4:08 ` Pratyush Anand
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=54DD043D.8000801@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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).