public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>
Subject: [PATCH RT 1/3] spinlock/rt: Include bug.h in spinlock_rt.h to satisfy BUG() usage
Date: Fri, 22 Jun 2012 23:05:49 -0400	[thread overview]
Message-ID: <20120623030638.813391214@goodmis.org> (raw)
In-Reply-To: 20120623030548.500374594@goodmis.org

[-- Attachment #1: 0001-spinlock-rt-Include-bug.h-in-spinlock_rt.h-to-satisf.patch --]
[-- Type: text/plain, Size: 762 bytes --]

From: Steven Rostedt <srostedt@redhat.com>

Some archs (powerpc) failed to compile because of the reference to
BUG() in spinlock_rt.h. Although bug.h is included in many headers,
if spinlock.h is included in a C file before that, it will fail to
compile.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
 include/linux/spinlock_rt.h |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/spinlock_rt.h b/include/linux/spinlock_rt.h
index 3b555b4..0618387 100644
--- a/include/linux/spinlock_rt.h
+++ b/include/linux/spinlock_rt.h
@@ -5,6 +5,8 @@
 #error Do not include directly. Use spinlock.h
 #endif
 
+#include <linux/bug.h>
+
 extern void
 __rt_spin_lock_init(spinlock_t *lock, char *name, struct lock_class_key *key);
 
-- 
1.7.10



  reply	other threads:[~2012-06-23  3:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23  3:05 [PATCH RT 0/3] [ANNOUNCE] 3.4.3-rt12-rc1 stable review Steven Rostedt
2012-06-23  3:05 ` Steven Rostedt [this message]
2012-06-23  3:05 ` [PATCH RT 2/3] Oops during Init IRQ Steven Rostedt
2012-06-23 10:59   ` Thomas Gleixner
2012-06-23 13:42     ` Steven Rostedt
2012-06-23  3:05 ` [PATCH RT 3/3] Linux 3.4.3-rt12-rc1 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=20120623030638.813391214@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=C.Emde@osadl.org \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --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