From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [patch, -rc5-mm2] lock validator: early_boot_irqs_[on|off]() build fix
Date: Fri, 2 Jun 2006 15:56:30 +0200 [thread overview]
Message-ID: <20060602135630.GA6676@elte.hu> (raw)
Subject: lock validator: early_boot_irqs_[on|off]() build fix
From: Ingo Molnar <mingo@elte.hu>
fix build bug if CONFIG_TRACE_IRQFLAGS is off: the existence of
early_boot_irqs_[on|off]() depends on CONFIG_TRACE_IRQFLAGS,
not on CONFIG_LOCKDEP.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
include/linux/lockdep.h | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
Index: linux/include/linux/lockdep.h
===================================================================
--- linux.orig/include/linux/lockdep.h
+++ linux/include/linux/lockdep.h
@@ -210,9 +210,6 @@ extern void lockdep_release(struct lockd
# define INIT_LOCKDEP .lockdep_recursion = 0,
-extern void early_boot_irqs_off(void);
-extern void early_boot_irqs_on(void);
-
#else /* LOCKDEP */
# define lockdep_init() do { } while (0)
# define lockdep_info() do { } while (0)
@@ -222,14 +219,20 @@ extern void early_boot_irqs_on(void);
# define INIT_LOCKDEP
# define lockdep_reset() do { debug_locks = 1; } while (0)
# define lockdep_free_key_range(start, size) do { } while (0)
-# define early_boot_irqs_off() do { } while (0)
-# define early_boot_irqs_on() do { } while (0)
/*
* The type key takes no space if lockdep is disabled:
*/
struct lockdep_type_key { };
#endif /* !LOCKDEP */
+#ifdef CONFIG_TRACE_IRQFLAGS
+extern void early_boot_irqs_off(void);
+extern void early_boot_irqs_on(void);
+#else
+# define early_boot_irqs_off() do { } while (0)
+# define early_boot_irqs_on() do { } while (0)
+#endif
+
/*
* For trivial one-depth nesting of a lock-type, the following
* global define can be used. (Subsystems with multiple levels
reply other threads:[~2006-06-02 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060602135630.GA6676@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome