linux-metag.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Bin <huawei.libin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org,
	james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org
Cc: linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	guohanjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
	huawei.libin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org
Subject: [PATCH] metag: ftrace: remove the misleading comment for ftrace_dyn_arch_init
Date: Mon, 28 Dec 2015 16:34:07 +0800	[thread overview]
Message-ID: <1451291647-10478-1-git-send-email-huawei.libin@huawei.com> (raw)

ftrace_dyn_arch_init no longer in kstop_machine, so remove the
corresponding comment.

Signed-off-by: Li Bin <huawei.libin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
---
 arch/metag/kernel/ftrace.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/arch/metag/kernel/ftrace.c b/arch/metag/kernel/ftrace.c
index ed1d685..4abcae4 100644
--- a/arch/metag/kernel/ftrace.c
+++ b/arch/metag/kernel/ftrace.c
@@ -116,7 +116,6 @@ int ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
 	return ftrace_modify_code(ip, old, new);
 }
 
-/* run from kstop_machine */
 int __init ftrace_dyn_arch_init(void)
 {
 	return 0;
-- 
1.7.1

             reply	other threads:[~2015-12-28  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28  8:34 Li Bin [this message]
     [not found] ` <1451291647-10478-1-git-send-email-huawei.libin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-01-04 22:48   ` [PATCH] metag: ftrace: remove the misleading comment for ftrace_dyn_arch_init James Hogan

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=1451291647-10478-1-git-send-email-huawei.libin@huawei.com \
    --to=huawei.libin-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=guohanjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org \
    --cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).