From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
gregkh@suse.de, bcollins@bluecherry.net
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH -next] staging/solo: add delay.h header
Date: Fri, 2 Jul 2010 16:44:13 -0700 [thread overview]
Message-ID: <20100702164413.20171588.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100702163505.272e6fca.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
Several solo drivers need <linux/delay.h>, so add it to the
private solo6010.h header file.
drivers/staging/solo6x10/solo6010-core.c:191: error: implicit declaration of function 'mdelay'
drivers/staging/solo6x10/solo6010-tw28.c:181: error: implicit declaration of function 'msleep_interruptible'
drivers/staging/solo6x10/solo6010-gpio.c:78: error: implicit declaration of function 'udelay'
drivers/staging/solo6x10/solo6010-v4l2-enc.c:254: error: implicit declaration of function 'mdelay'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/staging/solo6x10/solo6010.h | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20100702.orig/drivers/staging/solo6x10/solo6010.h
+++ linux-next-20100702/drivers/staging/solo6x10/solo6010.h
@@ -26,6 +26,7 @@
#include <linux/semaphore.h>
#include <linux/mutex.h>
#include <linux/list.h>
+#include <linux/delay.h>
#include <linux/wait.h>
#include <asm/io.h>
#include <asm/atomic.h>
prev parent reply other threads:[~2010-07-02 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 6:35 linux-next: Tree for July 2 Stephen Rothwell
2010-07-02 16:39 ` linux-next: Tree for July 2 (touchscreen/ad7879) Randy Dunlap
2010-07-02 16:58 ` Dmitry Torokhov
2010-07-03 20:17 ` Dmitry Torokhov
2010-07-02 23:44 ` Randy Dunlap [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=20100702164413.20171588.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=bcollins@bluecherry.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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