From: Masami Hiramatsu <mhiramat@redhat.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] kprobes: remove intialization of static per-cpu variable
Date: Thu, 12 Jun 2008 21:47:30 +0000 [thread overview]
Message-ID: <48519972.8040203@redhat.com> (raw)
In-Reply-To: <20080612210719.GB3283@damson.getinternet.no>
Hi Vegard,
Since David who is the sparc kprobes maintainer confirmed this change,
I think it can go.
Acked-by: Masami Hiramatsu <mhiramat@redhat.com>
Vegard Nossum wrote:
> From: Vegard Nossum <vegard.nossum@gmail.com>
> Date: Thu, 12 Jun 2008 22:02:01 +0200
> Subject: [PATCH] kprobes: remove intialization of static per-cpu variable
>
> Cc: Masami Hiramatsu <mhiramat@redhat.com>
> Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
> ---
> kernel/kprobes.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index 1e0250c..04a0c36 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -70,7 +70,7 @@ static bool kprobe_enabled;
>
> DEFINE_MUTEX(kprobe_mutex); /* Protects kprobe_table */
> DEFINE_SPINLOCK(kretprobe_lock); /* Protects kretprobe_inst_table */
> -static DEFINE_PER_CPU(struct kprobe *, kprobe_instance) = NULL;
> +static DEFINE_PER_CPU(struct kprobe *, kprobe_instance);
>
> /*
> * Normally, functions that we'd want to prohibit kprobes in, are marked
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
prev parent reply other threads:[~2008-06-12 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 21:07 [PATCH] kprobes: remove intialization of static per-cpu variable Vegard Nossum
2008-06-12 21:47 ` 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=48519972.8040203@redhat.com \
--to=mhiramat@redhat.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 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.