From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: linux-next@vger.kernel.org.
Cc: linux-mips@linux-mips.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org, David H?rdeman <david@hardeman.nu>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linuxppc-dev@ozlabs.org, linux-m68k@lists.linux-m68k.org,
Paul Mundt <lethal@linux-sh.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] media/IR: Add missing include file to rc-map.c
Date: Fri, 14 May 2010 13:22:41 +0200 [thread overview]
Message-ID: <201005141322.41370.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20100514060240.GD12002@linux-sh.org>
From: Peter Huewe <peterhuewe@gmx.de>
This patch adds a missing include linux/delay.h to prevent
build failures[1-5]
Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
---
Forwarded to linux-next mailing list -
breakage still exists in linux-next of 20100514 - please apply
KernelVersion: linux-next-20100505
References:
[1] http://kisskb.ellerman.id.au/kisskb/buildresult/2571452/
[2] http://kisskb.ellerman.id.au/kisskb/buildresult/2571188/
[3] http://kisskb.ellerman.id.au/kisskb/buildresult/2571479/
[4] http://kisskb.ellerman.id.au/kisskb/buildresult/2571429/
[5] http://kisskb.ellerman.id.au/kisskb/buildresult/2571432/
drivers/media/IR/rc-map.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/IR/rc-map.c b/drivers/media/IR/rc-map.c
index caf6a27..46a8f15 100644
--- a/drivers/media/IR/rc-map.c
+++ b/drivers/media/IR/rc-map.c
@@ -14,6 +14,7 @@
#include <media/ir-core.h>
#include <linux/spinlock.h>
+#include <linux/delay.h>
/* Used to handle IR raw handler extensions */
static LIST_HEAD(rc_map_list);
--
1.6.4.4
next prev parent reply other threads:[~2010-05-14 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 15:20 [PATCH] media/IR: Add missing include file to rc-map.c Peter Hüwe
2010-05-11 18:42 ` Peter Hüwe
2010-05-14 6:02 ` Paul Mundt
2010-05-14 11:22 ` Peter Hüwe [this message]
2010-05-14 11:26 ` Peter Hüwe
2010-05-14 12:53 ` Stephen Rothwell
2010-05-16 1:54 ` Mauro Carvalho Chehab
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=201005141322.41370.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=david@hardeman.nu \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org. \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mchehab@infradead.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;
as well as URLs for NNTP newsgroup(s).