From: Ingo Molnar <mingo@elte.hu>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] kernel: trace: trace_kprobe.c: removed duplicated #include
Date: Sat, 16 Oct 2010 15:11:54 +0200 [thread overview]
Message-ID: <20101016131154.GC8751@elte.hu> (raw)
In-Reply-To: <1287170842-20279-1-git-send-email-andrea.gelmini@gelma.net>
* Andrea Gelmini <andrea.gelmini@gelma.net> wrote:
> Removed linux/uaccess.h
>
> Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
> ---
> kernel/trace/trace_kprobe.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> index 544301d..c5fb747 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -18,7 +18,6 @@
> */
>
> #include <linux/module.h>
> -#include <linux/uaccess.h>
> #include <linux/kprobes.h>
> #include <linux/seq_file.h>
> #include <linux/slab.h>
> @@ -479,7 +478,7 @@ struct probe_arg {
> struct trace_probe {
> struct list_head list;
> struct kretprobe rp; /* Use rp.kp for kprobe use */
> - unsigned long nhit;
> + unsigned long nhit;
> unsigned int flags; /* For TP_FLAG_* */
> const char *symbol; /* symbol name */
> struct ftrace_event_class class;
If you look at the actual code there's also other problems with the
vertical spacing of this and other structures (fetch_param, fetch_type,
trace_kprobe, etc.) defined here. Would be nice if you could check the
whole file and fix those too.
Thanks,
Ingo
prev parent reply other threads:[~2010-10-16 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 19:27 [PATCH] kernel: trace: trace_kprobe.c: removed duplicated #include Andrea Gelmini
2010-10-15 19:55 ` Mathieu Desnoyers
2010-10-16 13:11 ` Ingo Molnar [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=20101016131154.GC8751@elte.hu \
--to=mingo@elte.hu \
--cc=andrea.gelmini@gelma.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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