From: Pekka Enberg <penberg@cs.helsinki.fi>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
penberg@cs.helsinki.fi, eduard.munteanu@linux360.ro,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:tracing/kmemtrace] kmemtrace: fix build when CONFIG_KMEMTRACE is disabled
Date: Tue, 24 Mar 2009 12:03:36 GMT [thread overview]
Message-ID: <tip-ebe7ac8e115e6b6e1f4c2a177ba718f43b6bd23e@git.kernel.org> (raw)
In-Reply-To: <1237889858.25315.75.camel@penberg-laptop>
Commit-ID: ebe7ac8e115e6b6e1f4c2a177ba718f43b6bd23e
Gitweb: http://git.kernel.org/tip/ebe7ac8e115e6b6e1f4c2a177ba718f43b6bd23e
Author: Pekka Enberg <penberg@cs.helsinki.fi>
AuthorDate: Tue, 24 Mar 2009 12:17:38 +0200
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 24 Mar 2009 11:31:51 +0100
kmemtrace: fix build when CONFIG_KMEMTRACE is disabled
Impact: fix build
This patch fixes the following allnoconfig failure:
init/built-in.o: In function `start_kernel':
(.init.text+0x669): undefined reference to `kmemtrace_init'
Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
LKML-Reference: <1237889858.25315.75.camel@penberg-laptop>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
include/trace/kmemtrace.h | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/include/trace/kmemtrace.h b/include/trace/kmemtrace.h
index 7514476..28ee69f 100644
--- a/include/trace/kmemtrace.h
+++ b/include/trace/kmemtrace.h
@@ -12,7 +12,13 @@
#include <linux/tracepoint.h>
#include <linux/types.h>
+#ifdef CONFIG_KMEMTRACE
extern void kmemtrace_init(void);
+#else
+static inline void kmemtrace_init(void)
+{
+}
+#endif
DECLARE_TRACE(kmalloc,
TP_PROTO(unsigned long call_site,
prev parent reply other threads:[~2009-03-24 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 10:17 [PATCH] kmemtrace: fix build when CONFIG_KMEMTRACE is disabled Pekka Enberg
2009-03-24 12:03 ` Pekka Enberg [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=tip-ebe7ac8e115e6b6e1f4c2a177ba718f43b6bd23e@git.kernel.org \
--to=penberg@cs.helsinki.fi \
--cc=eduard.munteanu@linux360.ro \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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