From: Jason Baron <jbaron@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
mathieu.desnoyers@polymtl.ca, hpa@zytor.com, tglx@linutronix.de,
rostedt@goodmis.org, andi@firstfloor.org, roland@redhat.com,
rth@redhat.com, mhiramat@redhat.com, fweisbec@gmail.com,
avi@redhat.com, vgoyal@redhat.com, sam@ravnborg.org,
tony@bakeyournoodle.com
Subject: Re: [PATCH 00/12] jump label v10
Date: Wed, 28 Jul 2010 16:42:26 -0400 [thread overview]
Message-ID: <20100728204225.GB28992@redhat.com> (raw)
In-Reply-To: <20100728.132427.35841081.davem@davemloft.net>
On Wed, Jul 28, 2010 at 01:24:27PM -0700, David Miller wrote:
> > Patches are against Ingo's latest -tip tree.
>
> After applying patch #5:
>
> kernel/kprobes.c: In function 'register_kprobe':
> kernel/kprobes.c:1145:6: error: implicit declaration of function 'jump_label_text_reserved'
> make[1]: *** [kernel/kprobes.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make: *** [kernel] Error 2
ok,
Not sure exactly what your .config is, but pulling in jump_label.h
explicitly into kprobes.c should fix that. if it doesn't please post
your .config.
diff --git a/kernel/kprobes.c b/kernel/kprobes.c
index 2f9bea6..a53bff3 100644
--- a/kernel/kprobes.c
+++ b/kernel/kprobes.c
@@ -47,6 +47,7 @@
#include <linux/memory.h>
#include <linux/ftrace.h>
#include <linux/cpu.h>
+#include <linux/jump_label.h>
#include <asm-generic/sections.h>
#include <asm/cacheflush.h>
thanks,
-Jason
next prev parent reply other threads:[~2010-07-28 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 20:53 [PATCH 00/12] jump label v10 Jason Baron
2010-07-27 20:54 ` [PATCH 01/12] jump label v10: base patch Jason Baron
2010-07-27 20:54 ` [PATCH 02/12] jump label v10: add module support Jason Baron
2010-07-27 20:54 ` [PATCH 03/12] jump label v10: move ftrace_dyn_arch_init to common code Jason Baron
2010-07-27 20:54 ` [PATCH 04/12] jump label v10: initialize workqueue tracepoints *before* they are registered Jason Baron
2010-07-27 20:54 ` [PATCH 05/12] jump label v10: jump_label_text_reserved() to reserve our jump points Jason Baron
2010-07-27 20:54 ` [PATCH 06/12] jump label v10: convert jump label to use a key Jason Baron
2010-07-28 20:37 ` David Miller
2010-07-27 20:54 ` [PATCH 07/12] jump label v10: use lib/sort.c Jason Baron
2010-07-28 20:40 ` David Miller
2010-07-27 20:54 ` [PATCH 08/12] jump label v10: tracepoint support Jason Baron
2010-07-27 20:54 ` [PATCH 09/12] jump label v10: convert dynamic debug to use jump labels Jason Baron
2010-07-27 20:54 ` [PATCH 10/12] jump label v10: x86 support Jason Baron
2010-07-27 20:54 ` [PATCH 11/12] jump label v10: add sparc64 support Jason Baron
2010-07-27 20:54 ` [PATCH 12/12] jump label v10: add docs Jason Baron
2010-07-28 19:34 ` [PATCH 00/12] jump label v10 David Miller
2010-07-28 20:14 ` Jason Baron
2010-07-28 20:24 ` David Miller
2010-07-28 20:42 ` Jason Baron [this message]
2010-07-28 21:09 ` David Miller
2010-07-29 5:25 ` David Miller
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=20100728204225.GB28992@redhat.com \
--to=jbaron@redhat.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rth@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=tony@bakeyournoodle.com \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox