From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [origin tree build failure] [PATCH] headers: Fix build in drivers/pci/hotplug/cpqphp.h
Date: Mon, 12 Oct 2009 10:30:33 +0200 [thread overview]
Message-ID: <20091012083033.GA31206@elte.hu> (raw)
In-Reply-To: <20091012082950.GA2270@elte.hu>
Fix:
drivers/pci/hotplug/cpqphp.h: In function ‘wait_for_ctrl_irq’:
drivers/pci/hotplug/cpqphp.h:730: error: implicit declaration of function ‘signal_pending’
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
drivers/pci/hotplug/cpqphp.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/hotplug/cpqphp.h b/drivers/pci/hotplug/cpqphp.h
index 5383600..9c6a9fd 100644
--- a/drivers/pci/hotplug/cpqphp.h
+++ b/drivers/pci/hotplug/cpqphp.h
@@ -32,6 +32,7 @@
#include <asm/io.h> /* for read? and write? functions */
#include <linux/delay.h> /* for delays */
#include <linux/mutex.h>
+#include <linux/sched.h> /* for signal_pending() */
#define MY_NAME "cpqphp"
next prev parent reply other threads:[~2009-10-12 8:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 21:58 Linux 2.6.32-rc4 Linus Torvalds
2009-10-12 7:42 ` [origin tree build failure] [PATCH] Revert "USB: musb: make HAVE_CLK support optional" Ingo Molnar
2009-10-12 13:05 ` Mike Frysinger
2009-10-12 14:29 ` Greg KH
2009-10-12 14:39 ` Mike Frysinger
2009-10-12 15:00 ` Ingo Molnar
2009-10-12 15:09 ` Mike Frysinger
2009-10-12 13:49 ` [PATCH] USB: musb: invert arch depend string Mike Frysinger
2009-10-12 14:28 ` Greg KH
2009-10-12 15:02 ` Ingo Molnar
2009-10-12 8:05 ` [crash] NULL pointer dereference at IP: [<ffffffff812e9ccb>] uart_close+0x2a/0x1e4 Ingo Molnar
2009-10-12 9:19 ` Ingo Molnar
2009-10-12 9:27 ` Ingo Molnar
2009-10-12 11:25 ` Ingo Molnar
2009-10-12 11:45 ` Alan Cox
2009-10-12 11:55 ` Ingo Molnar
2009-10-12 12:22 ` Ingo Molnar
2009-10-12 13:06 ` Alan Cox
2009-10-12 14:23 ` Ingo Molnar
2009-10-12 16:19 ` Linus Torvalds
2009-10-12 16:26 ` Ingo Molnar
2009-10-12 16:28 ` Ingo Molnar
2009-10-12 16:37 ` Linus Torvalds
2009-10-12 17:13 ` [PATCH] tty, serial: Fix race and NULL check in uart_close() Ingo Molnar
2009-10-12 8:29 ` Linux 2.6.32-rc4 Ingo Molnar
2009-10-12 8:30 ` Ingo Molnar [this message]
2009-10-12 8:32 ` [origin tree build failure] [PATCH] headers: Fix build in drivers/char/rtc.c Ingo Molnar
2009-10-12 8:40 ` [origin tree build failure] [PATCH] headers: Fix build in drivers/net/wan/pci200syn.c Ingo Molnar
2009-10-12 9:11 ` [origin tree build failure] [PATCH] headers: Fix build in drivers/net/wan/n2.c Ingo Molnar
2009-10-12 9:16 ` [origin tree build failure] [PATCH] headers: Fix build in drivers/net/wan/c101.c Ingo Molnar
2009-10-12 10:06 ` [origin tree build failure] [PATCH] headers: Fix build in drivers/char/genrtc.c Ingo Molnar
2009-10-12 13:29 ` Linux 2.6.32-rc4 Alexey Dobriyan
2009-10-12 9:43 ` Ingo Molnar
2009-10-12 13:34 ` Alexey Dobriyan
2009-10-12 9:48 ` Ingo Molnar
2009-10-12 14:22 ` [origin tree build failure] [PATCH] headers: Fix build in drivers/char/sonypi.c Ingo Molnar
2009-10-12 13:01 ` Linux 2.6.32-rc4 Thomas Meyer
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=20091012083033.GA31206@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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