From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] kprobes/x86: remove extern from function definition
Date: Mon, 05 Mar 2012 02:55:33 +0000 [thread overview]
Message-ID: <4F542B25.6090901@hitachi.com> (raw)
In-Reply-To: <1330791128-3293-1-git-send-email-emilgoode@gmail.com>
(2012/03/04 1:12), Emil Goode wrote:
> Functions with definition should not be declared extern.
>
> sparse warns:
> arch/x86/kernel/kprobes.c:1489:13: warning:
> function 'arch_unoptimize_kprobes' with external linkage
> has definition
>
> Signed-off-by: Emil Goode <emilgoode@gmail.com>
Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Thank you!
> ---
> arch/x86/kernel/kprobes.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/kprobes.c b/arch/x86/kernel/kprobes.c
> index 7da647d..f55c28e 100644
> --- a/arch/x86/kernel/kprobes.c
> +++ b/arch/x86/kernel/kprobes.c
> @@ -1486,8 +1486,8 @@ static void __kprobes setup_unoptimize_kprobe(struct text_poke_param *tprm,
> * Recover original instructions and breakpoints from relative jumps.
> * Caller must call with locking kprobe_mutex.
> */
> -extern void arch_unoptimize_kprobes(struct list_head *oplist,
> - struct list_head *done_list)
> +void arch_unoptimize_kprobes(struct list_head *oplist,
> + struct list_head *done_list)
> {
> struct optimized_kprobe *op, *tmp;
> int c = 0;
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2012-03-05 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 16:12 [PATCH] kprobes/x86: remove extern from function definition Emil Goode
2012-03-05 2:55 ` Masami Hiramatsu [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=4F542B25.6090901@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=kernel-janitors@vger.kernel.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).