From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Abhishek Sagar <sagar.abhishek@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@redhat.com>,
akpm@linux-foundation.org
Subject: Re: [PATCH] kprobes: remove redundant config check
Date: Wed, 11 Jun 2008 09:29:55 +0530 [thread overview]
Message-ID: <20080611035955.GA19154@in.ibm.com> (raw)
In-Reply-To: <484EB61E.7050509@gmail.com>
On Tue, Jun 10, 2008 at 10:43:02PM +0530, Abhishek Sagar wrote:
> Hi,
>
> I noticed that there's a CONFIG_KPROBES check inside kernel/kprobes.c,
> which seems redundant. Can be removed?
>
> Diff'd against v2.6.26-rc5.
>
>
> Signed-off-by: Abhishek Sagar <sagar.abhishek@gmail.com>
> ---
> remove redundant CONFIG_KPROBES check.
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index 1e0250c..2b2cae2 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -1283,13 +1283,8 @@ EXPORT_SYMBOL_GPL(register_jprobe);
> EXPORT_SYMBOL_GPL(unregister_jprobe);
> EXPORT_SYMBOL_GPL(register_jprobes);
> EXPORT_SYMBOL_GPL(unregister_jprobes);
> -#ifdef CONFIG_KPROBES
> EXPORT_SYMBOL_GPL(jprobe_return);
> -#endif
> -
> -#ifdef CONFIG_KPROBES
> EXPORT_SYMBOL_GPL(register_kretprobe);
> EXPORT_SYMBOL_GPL(unregister_kretprobe);
> EXPORT_SYMBOL_GPL(register_kretprobes);
> EXPORT_SYMBOL_GPL(unregister_kretprobes);
> -#endif
Abhishek,
This was intentional (to take care of some gcc 4.2 issues). See commit
cd5bfea278987ebfe60f3ff92a01696b17c4f978 (fix compilation with gcc 4.2)
from Peter Chubb for details.
Ananth
next prev parent reply other threads:[~2008-06-11 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:13 [PATCH] kprobes: remove redundant config check Abhishek Sagar
2008-06-10 19:35 ` Masami Hiramatsu
2008-06-11 3:59 ` Ananth N Mavinakayanahalli [this message]
2008-06-11 5:53 ` Abhishek Sagar
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=20080611035955.GA19154@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=sagar.abhishek@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.