From: Steven Rostedt <rostedt@goodmis.org>
To: guoren@kernel.org
Cc: linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>,
mingo@redhat.co, linux-arm-kernel@lists.infradead.org,
linux@armlinux.org.uk
Subject: Re: [PATCH] arm/ftrace: Remove duplicate function
Date: Fri, 20 Mar 2020 10:11:59 -0400 [thread overview]
Message-ID: <20200320101159.60037586@gandalf.local.home> (raw)
In-Reply-To: <20200320065340.32685-1-guoren@kernel.org>
On Fri, 20 Mar 2020 14:53:40 +0800
guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> There is no arch implementation of ftrace_arch_code_modify_prepare in arm,
> so just use the __weak one in kernel/trace/ftrace.c.
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
>
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> ---
> arch/arm/kernel/ftrace.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/arm/kernel/ftrace.c b/arch/arm/kernel/ftrace.c
> index 10499d44964a..f66ade28eb8a 100644
> --- a/arch/arm/kernel/ftrace.c
> +++ b/arch/arm/kernel/ftrace.c
> @@ -56,11 +56,6 @@ static unsigned long adjust_address(struct dyn_ftrace *rec, unsigned long addr)
> return addr;
> }
>
> -int ftrace_arch_code_modify_prepare(void)
> -{
> - return 0;
> -}
> -
> int ftrace_arch_code_modify_post_process(void)
> {
> /* Make sure any TLB misses during machine stop are cleared. */
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-03-20 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 6:53 [PATCH] arm/ftrace: Remove duplicate function guoren
2020-03-20 14:11 ` Steven Rostedt [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=20200320101159.60037586@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.co \
/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