From: Paul Mundt <lethal@linux-sh.org>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
Jon Masters <jcm@jonmasters.org>
Cc: linux-next@vger.kernel.org
Subject: [PATCH -next 2/2] hwlat_detector: select RING_BUFFER.
Date: Thu, 25 Jun 2009 14:31:17 +0900 [thread overview]
Message-ID: <20090625053117.GC19944@linux-sh.org> (raw)
In-Reply-To: <20090625053012.GB19944@linux-sh.org>
The hwlat_detector broke quite a few of the sh module builds:
ERROR: "ring_buffer_write" [drivers/misc/hwlat_detector.ko] undefined!
ERROR: "ring_buffer_reset" [drivers/misc/hwlat_detector.ko] undefined!
ERROR: "__ring_buffer_alloc" [drivers/misc/hwlat_detector.ko] undefined!
ERROR: "ring_buffer_event_data" [drivers/misc/hwlat_detector.ko] undefined!
ERROR: "ring_buffer_consume" [drivers/misc/hwlat_detector.ko] undefined!
ERROR: "ring_buffer_free" [drivers/misc/hwlat_detector.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
This fixes it up by selecting RING_BUFFER outright.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Cc: Jon Masters <jcm@jonmasters.org>
---
drivers/misc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 4448a83..f51ba7b 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -79,6 +79,7 @@ config IBM_ASM
config HWLAT_DETECTOR
tristate "Testing module to detect hardware-induced latencies"
depends on DEBUG_FS
+ select RING_BUFFER
default m
---help---
A simple hardware latency detector. Use this module to detect
next prev parent reply other threads:[~2009-06-25 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 5:30 [PATCH -next 1/2] ring-buffer: Really make it generic Paul Mundt
2009-06-25 5:31 ` Paul Mundt [this message]
2009-06-25 7:09 ` Jon Masters
2009-06-25 7:16 ` Paul Mundt
2009-06-25 8:32 ` Ingo Molnar
2009-06-25 9:16 ` [tip:tracing/urgent] ring-buffer: Make it generally available tip-bot for Paul Mundt
2009-06-25 12:40 ` Steven Rostedt
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=20090625053117.GC19944@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=jcm@jonmasters.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.